Live data from Hacker News

When coding style survives compilation: De-anonymizing programmers from binaries

freedom-to-tinker.com

31–40 of 74 posts

Re: When coding style survives compilation: De-anonymizing programmers from binaries

#31
post #9

Interesting but if your code is open source a lot of people will be contributing to it bringing in their own style. Depending on how popular the code is your fingerprint could be completely hidden amongst hundreds.

I will pay you to do upvote. Reach me on Skyp: cobalmx

Re: When coding style survives compilation: De-anonymizing programmers from binaries

#32
This is an interesting article, but there's one part that I don't really understand: 'After scaling up the approach by increasing the dataset size, we de-anonymize 600 programmers with 52% accuracy.'.

Isn't 52% close to a random guess? I don't get how this ties in with the rest of the paragraph either.

Re: When coding style survives compilation: De-anonymizing programmers from binaries

#34
post #32

This is an interesting article, but there's one part that I don't really understand: 'After scaling up the approach by increasing the dataset size, we de-anonymize 600 programmers with 52% accuracy.'. Isn't 52% close to a random guess? I don't get how this ties in with the rest of the paragraph either.

No, a random guess would give you 0.16% accuracy.

Re: When coding style survives compilation: De-anonymizing programmers from binaries

#36
post #32

This is an interesting article, but there's one part that I don't really understand: 'After scaling up the approach by increasing the dataset size, we de-anonymize 600 programmers with 52% accuracy.'. Isn't 52% close to a random guess? I don't get how this ties in with the rest of the paragraph either.

If they were saying that in 52% of the cases, they could guess the correct choice out of 600, then random chance alone would have been If they were saying that in 52% of cases, they could guess if some code did or did not belong to a given programmer, then it is basically a random guess.

Re: When coding style survives compilation: De-anonymizing programmers from binaries

#37
post #32

This is an interesting article, but there's one part that I don't really understand: 'After scaling up the approach by increasing the dataset size, we de-anonymize 600 programmers with 52% accuracy.'. Isn't 52% close to a random guess? I don't get how this ties in with the rest of the paragraph either.

Considering there are 600 programmers, 0.166% (1/600) would be random guess.

Re: When coding style survives compilation: De-anonymizing programmers from binaries

#38
post #2

Maybe we can use this method to find Satoshi, if he uses github.

In the ccc talk, the author actually talk about this. But she mentioned that their primary suspect doesn't have any code samples online, and they left it at that.

Their code should be online, but I am not sure what exactly is there though.

Re: When coding style survives compilation: De-anonymizing programmers from binaries

#39
post #23
post #4

Well, this puts a damper on my plan to create a secret identity on the internet under which I release software the way Banksy releases art. Unless I stop publicly writing software for a few years.

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.

Re: When coding style survives compilation: De-anonymizing programmers from binaries

#40
post #17

Earlier quoted context omitted.

As a professional, I tend to think a distinct coding style is bad. You should try to write a code that is plain and unsurprising and reproducible. To me, this study gives us another reason that we need a more uniform/standardized methodology and good education for the software industry.

Writing code that is plain, unsurprising, and reproducible not only is, itself, a style but also still leaves a lot of room for creativity/individuality.

Writing code is some ways a lot like writing in general. From the "elements of style" book:

> Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences, for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary parts. This requires not that the writer make all his sentences short, or that he avoid all detail and treat his subjects only in outline, but that he make every word tell.

https://en.wikipedia.org/wiki/The_Elements_of_Style

Post reply on HN