[ziles88]

I developed exactly this type of software, like 5 years ago. This is just click bait.

There are numerous ways to pack, and unpack code. It's really going nowhere tbh. It is mostly a meta-game between you and the person you'd expect to be RE your code. You think he's going to use a vm to RE? Then you prevent your code from running in that vm. You leave red herrings - like obscuring control flow, disabling ability to set breakpoints, delay unpacking, and phantom unpacking (where it only truly unpacks a certain percentage of the time)

There will NEVER be a way to prevent RE, and there will never be true polymorphic code. The world is still flock with people fluent in ASM and low level debugging, and all code will revel itself. Commercial protection suites aren't even where the real tricks come into play, malware and 'anti anti-virus' packers, are at the forefront of ingenuity. Even when the hardware is a part of the protection (a la Xbox) it still means nothing. I've seen some nasty stuff done to electronic payment devices by rather unsophisticated people, and those are some of the most hardened systems available (think self destruct if the casings are opened, or if JTAG is conntected)

[m8rl]

Hopefully you're right. For me this kind of endeavor sounds like a nightmare, being the absolute opposite of openess, open source, free standards and customer rights. All those "security" argumentations seem only a means to implement further undemocrative deployments.

[joshstrange]

Even the title reads like spam...

"Reverse engineers hate him!"

"One weird crypto trick to burn reverse engineers"