News for hackers. Stuff that matters.
Re:De-anonymizing programmers from executable binaries by xxs on Friday March 16, 2018 @10:06AM (#16600707)
Back in the late 80s/early 90s it was quite possible to tell the author looking at the disassembled portion of a virus. (when all viruses were virtually written in assembly)

I don't think much has changed.

Re:De-anonymizing programmers from executable binaries by EvanAnderson on Friday March 16, 2018 @11:42AM (#16601390)
Came here to say the same thing. Back in the early 90's one of my friends spent time obsessively studying the personal nuance of code attributed to The Dark Avenger. Even in code that had obviously been optimized bits of personal nuance leak through. It seems very intuitive that compiled languages, being more expressive, would leak more personal nuance.
Re:De-anonymizing programmers from executable binaries by xxs on Friday March 16, 2018 @01:10PM (#16602135)
Well that was easy, given the signature of triple 6 :D (although that part dropped due to space considerations)
Re:De-anonymizing programmers from executable binaries by bitwize on Friday March 16, 2018 @01:40PM (#16602402)
"Man, this thing is so lean and clean."

"Yeah, it's like a hacker wrote it."

"That's ill, man. It's incomplete!"

Re:De-anonymizing programmers from executable binaries by John_KZ on Saturday March 17, 2018 @01:31PM (#16608034)
A lot has changed. Now a team of security experts hired by governments or large organizations write their viruses to look like they originated from someone else when the victims disassemble them and look for clues.