News for hackers. Stuff that matters.
Re:GitHub Security Update: Reused Password Attack by spion on Thursday June 16, 2016 @06:12AM (#11915132)
Thats cool! Does it use simple concatenation or HMAC?
Re:GitHub Security Update: Reused Password Attack by austerity on Thursday June 16, 2016 @06:20AM (#11915160)
It's simple concatenation. The exact algorithm is described at the bottom of the page so that one could reproduce it (and their passwords) independently.
Re:GitHub Security Update: Reused Password Attack by spion on Thursday June 16, 2016 @06:25AM (#11915184)
What about taking the 128 MSB vs 128 LSB, is there any research into how secure that is?
Re:GitHub Security Update: Reused Password Attack by austerity on Thursday June 16, 2016 @07:10AM (#11915335)
I vaguely remember giving it some consideration. But the bigger point is that my judgement on these things is not to be trusted since I'm just an application developer and not a crypto expert.
Re:GitHub Security Update: Reused Password Attack by spion on Saturday June 18, 2016 @07:13PM (#11931054)
Yeah thats the thing, I'm not a crypto expert either but I'd love to use it. But if it gets popular, and there is an accidental mistake that actually makes it easy to guess passwords, I don't want to risk that happening.
Re:GitHub Security Update: Reused Password Attack by spion on Tuesday June 21, 2016 @08:43PM (#11950742)
Good news. Did a bit of investigation, it seems like this could be vulnerable to a length extension attack [1] (though the attack its still pretty useless in this particular case) but it appears that truncating is both safe and takes care of length extension attacks! [2]

[1]: https://en.wikipedia.org/wiki/Length_extension_attack

[2]: https://crypto.stackexchange.com/questions/18606/is-xoring-a...