News for hackers. Stuff that matters.

A comment on Dirty tricks 6502 programmers use. Parent comment

Re:Dirty tricks 6502 programmers use by FartyMcFarter on Monday August 19, 2019 @07:24AM (#20736809)
One way to work around that is to allow authors to include comments in the code that gets hashed.

(I'm not sure if this particular competition did that)

[ Parent | on HN ]
Re:Dirty tricks 6502 programmers use by rusk on Monday August 19, 2019 @09:28AM (#20737525)
are you talking about padding it out to provoke a collision?

Remember, that at the end of the day, you still have to have actual working code …

[ Parent | on HN ]
Re:Dirty tricks 6502 programmers use by FartyMcFarter on Monday August 19, 2019 @05:22PM (#20741951)
No - what I mean is that if someone is worried that their code will be derived from their published hash by someone doing a brute-force attack, they can prevent (or make much harder) this brute-force attack by having comments in their source code.

I'm assuming here that the hashed string is the source code rather than the machine code.

[ Parent | on HN ]
Re:Dirty tricks 6502 programmers use by rusk on Tuesday August 20, 2019 @05:34AM (#20745105)
Ahhh - a salt
[ Parent | on HN ]