> If zlib goes in to an infinite 100% CPU loop, perhaps due to a zip bomb, you're still screwed as far as I can tell You can set CPU and wall time limits and the sandbox will be killed if it runs for longer. > A full…
LOL, haters gonna hate. So let's see... - BinDiff would work stand-alone if someone wrote an exporter for another disassembler (BinDiff uses https://github.com/google/binexport for that). - Closed source - yeah it…
Yeah that's a sore point :-/ The downloads are served via HTTPS, though. Also, publishing the SHA1 hashes over HTTP kind of defeats the purpose, so here they are again (HackerNews is HTTPS :)):…
Well it mostly works on 6.9 as well. Linux should work without any restrictions, but on Windows there were some IDA Qt changes that lead to some annoyances: - Can't reopen BinDiff windows after they were closed -…
Yup, we didn't bother with updating it in a looong while :-/
> If zlib goes in to an infinite 100% CPU loop, perhaps due to a zip bomb, you're still screwed as far as I can tell You can set CPU and wall time limits and the sandbox will be killed if it runs for longer. > A full…
LOL, haters gonna hate. So let's see... - BinDiff would work stand-alone if someone wrote an exporter for another disassembler (BinDiff uses https://github.com/google/binexport for that). - Closed source - yeah it…
Yeah that's a sore point :-/ The downloads are served via HTTPS, though. Also, publishing the SHA1 hashes over HTTP kind of defeats the purpose, so here they are again (HackerNews is HTTPS :)):…
Well it mostly works on 6.9 as well. Linux should work without any restrictions, but on Windows there were some IDA Qt changes that lead to some annoyances: - Can't reopen BinDiff windows after they were closed -…
Yup, we didn't bother with updating it in a looong while :-/