Re:A practical security guide for web developers
by minitech on Friday July 22, 2016 @02:50AM
(#12142112)
> Don't let HTTP GET requests modify state, ever. It's very difficult to prevent CSRF via HTTP GET.
Isn’t it exactly as difficult as any other method?
> Session keys are password-equivalents. Hash them with bcrypt or something before you store them.
bcrypt is overkill, especially for something that has to be checked every request; just use any SHA-2 (non-iterated). A session key should be long enough by far to resist brute force.
Isn’t it exactly as difficult as any other method?
> Session keys are password-equivalents. Hash them with bcrypt or something before you store them.
bcrypt is overkill, especially for something that has to be checked every request; just use any SHA-2 (non-iterated). A session key should be long enough by far to resist brute force.