Re:Movfuscator – A single-instruction C compiler
by haberman on Saturday August 27, 2016 @01:25PM
(#12373256)
Someone made something very clever, but it has no practical usefulness whatsoever. It is an interesting intellectual exercise. It's also very impressive that they could pull this off.
[ Parent
| on HN ]
Re:Movfuscator – A single-instruction C compiler
by SilasX on Saturday August 27, 2016 @01:42PM
(#12373332)
I would think it has some practical use as research in OISC (one-instruction set computing) processors, which are like the RISC model (do a smaller set of instructions so you can do them faster) on steroids.
Re:Movfuscator – A single-instruction C compiler
by lucb1e on Saturday August 27, 2016 @06:01PM
(#12374373)
No practical usefulness? It seems rather great for obfuscation, be it for evil (viruses) or good (license key verification -- which is deemed 'good' merely because they're legal, not because they're not a pain in the arse).
Re:Movfuscator – A single-instruction C compiler
by TelmoMenezes on Saturday August 27, 2016 @07:59PM
(#12374715)
Not really. Creating an algorithm for recovering the jumps and the intent of the various MOV patterns would be no more work than it was to write this. Particularly easier because one has access to the obfuscator's code, but I don't think it would be a major hurdle even without the source code.
Re:Movfuscator – A single-instruction C compiler
by lucb1e on Saturday August 27, 2016 @08:38PM
(#12374787)
Same could be said for most binaries: they're just compilations (usually with open source or freely available compilers) of C/C++ code. Shouldn't be too hard to reverse once you got all the patterns worked out.
I see your point though. I'm not very experienced on this and I'm sure some patterns can easily be recovered, but until someone goes through the effort it's still a considerable effort compared to being able to read the program normally, and even when someone does it's questionable whether the original can be recovered with some simple 1:1 translation.