News for hackers. Stuff that matters.
Re:Security advisory: Breach and Django by tomp on Tuesday August 06, 2013 @01:43PM (#6167988)
Well, technically you don't need to invalidate the earlier CSRF tokens. Saving a big number of CSRF tokens per user would of course require quite a lot of storage, but maybe you could devise some "clever" scheme, e.g. token = "n" + sha(user_secret + "n"), which would be random enough for preventing BREACH, but easy enough to check.
Re:Security advisory: Breach and Django by nwh on Tuesday August 06, 2013 @09:10PM (#6170237)
You'd want to have the secret last in the hash, otherwise you're open to hash extension attacks in some rare cases.