My suspicion is that most of these features wouldn't survive in an adversarial setting -- either by consciously changing your coding style or (better) using automated tools to rewrite your source code before compilation to alter the control flow structure (e.g., control flow flattening [1]).

http://reverseengineering.stackexchange.com/questions/2221/w...

Another option would be safety in numbers. Take a large executable written by someone else and wear its dead code like its your own skin. Hiding your true self in there somewhere.

That might be an interesting way to defeat it! Thanks.

I am not so sure that the coding style doesn't survive the automated tools. It's also about what features you implement and how you do it.

Running `strip` on the binary decreased classification accuracy by 12%. They quite correctly point out that this isn't a large drop, but strip is really the lowest of the low hanging fruit when it comes to code obfuscation. I'd expect much bigger drops from anything that's trying to make code harder to fingerprint.

> I release software the way Banksy releases art.

It's pretty easy to vandalize a wiki tho.

Wha

you can use another language

One of the points of the talk/article is that style survives compilation, obfuscation and optimization. I think (but the talk did not support that directly) that it would survive another language, at least to a certain degree.

I doubt that their system would be able to recognize programmers if their training samples in C and their test samples are in Haskell.