Re:Avast open-sources its machine-code decompiler
by bringtheaction on Wednesday December 13, 2017 @07:49AM
(#15913876)
> proof of concept
They've been working on this for 7 years they said so I don't think it counts as just a PoC.
Re:Avast open-sources its machine-code decompiler
by UncleEntity on Wednesday December 13, 2017 @07:47AM
(#15913867)
> Looks like it's also relying on LLVM for disassembly?
[wild speculation here] I suspect they're using llvm to go from an ast to c(++) code since they have tooling for stuff like that.
Now I have to find me a binary-blob kernel module that manufactures like to put out and see what the C code it spits out looks like -- another wasted day methinks...
Re:Avast open-sources its machine-code decompiler
by Tobba_ on Wednesday December 13, 2017 @02:34PM
(#15916848)
You could just ..uh.. acquire a copy of IDA that has the AMD64 decompiler. It's more mature and spits out C code of wildly varying readability, though only for one function at a time.
Re:Avast open-sources its machine-code decompiler
by Karliss on Wednesday December 13, 2017 @01:26PM
(#15916220)
Isn't it using capstone?
Re:Avast open-sources its machine-code decompiler
by Tobba_ on Wednesday December 13, 2017 @02:31PM
(#15916815)
Doesn't look that way? https://github.com/avast-tl/retdec/blob/master/src/bin2llvmi...
Capstone would probably be the best open-source choice for something like this though.
Re:Avast open-sources its machine-code decompiler
by Karliss on Wednesday December 13, 2017 @05:12PM
(#15918161)
There is also capstone2llvmir in https://github.com/avast-tl/retdec/tree/master/deps
Although, there's no way an AV company doesn't have its own disassembler, but those are almost always treated as trade secrets (especially the stuff that isn't in the spec / the spec is wrong). They'll probably hook it up to that before doing any real work with it themselves.