News for hackers. Stuff that matters.
Re:Security advisory: Breach and Django by homakov on Tuesday August 06, 2013 @06:00PM (#6169507)
Your UPDATE is right, attacker can probe a..z 2 times, and just choose the letter that was compressed in both of them, ignoring random compressions
Re:Security advisory: Breach and Django by gojomo on Tuesday August 06, 2013 @06:48PM (#6169717)
Thanks, but can you clarify... does that mean probing (a..z)×(a..z) (one pair per probe), so there's at least a giant increase in probing required per character? And perhaps even more each character in, since probing for the Nth character now requires (a..z)^(N-1) × (a..z)×(a..z) ?

(I'm guessing also, though, it may be possible to probabilistically probe multiple ranges of the secret at once... in a process that seems vaguely similar to forward-error-correction coding.)

Re:Security advisory: Breach and Django by homakov on Tuesday August 06, 2013 @06:19PM (#6169596)
also we need a reflector with 'value="' in the beginning https://twitter.com/homakov/status/364872768921165824/photo/...