News for hackers. Stuff that matters.
Re:The Tigress Diversifying C Virtualizer by tptacek on Sunday August 03, 2014 @12:42AM (#8127049)
That is correct. The author of this tool is an expert in that field, too; his book (Surreptitious Software) is solid.

I'm not sure what the subtext of your comment is, though. If it's "software like this is bad because it enables DRM", that's an odd position to take. If you don't want to obfuscate your code, don't run this transformer on it.

Re:The Tigress Diversifying C Virtualizer by userbinator on Sunday August 03, 2014 @07:45AM (#8127685)
I would never use such a tool on my software; the concern is that others will - especially malware authors, who have been obfuscating their creations for as long as malware has existed. Executable packers/encrypters already significantly frustrate analysis by security researchers and antivirus programs; more powerful obfuscation/diversification tools only make it harder to distinguish between benign and malicious software.

Obfuscation makes even legal reverse-engineering (as defined by the DMCA) difficult, meaning that threats like backdoors could become harder to discover. Amusingly enough, the definition of surreptitious that Google gives is quite relevant here: "kept secret, especially because it would not be approved of."

I wonder if these people who are pro-DRM ever find themselves in a situation where the systems they create are used against them, and reconsider the effects of their work.

Re:The Tigress Diversifying C Virtualizer by tptacek on Sunday August 03, 2014 @11:13AM (#8128122)
Tools like these show us what's possible (actually, as Collberg points out, this particular tool is more like training for learning what's possible; the frontier of this approach to software protection is way past it). This is science. It is weird to object to it. Should we instead pretend that it's not possible to effectively obfuscate code?