network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 7 months |
| seen | Feb 13 at 17:04 | |
| stats | profile views | 3 |
|
Feb 13 |
awarded | Scholar |
|
Feb 13 |
accepted | What security issues are there when reading cookie with .htaccess? |
|
Feb 13 |
comment |
What security issues are there when reading cookie with .htaccess? Thanks! This gives me what I was looking for. A single token for every user, but one that is not guessable. I should have thought of this, but unfortunately didn't. |
|
Feb 13 |
asked | What security issues are there when reading cookie with .htaccess? |
|
Sep 30 |
comment |
Is it secure to use bcrypt-generated salt in cookie to serve as token in place of a password? Thanks for the reply. I was looking at the likelihood of the cookie's being stolen on the one hand (remember, it is all SSL, secure, httponly, etc) vs. the relative unimportance of what is being protected on the other hand. And if you'll allow me a third hand, the relative effort in coding (remember, this is a hobby, not a day job or even a paying job). |
|
Sep 29 |
awarded | Student |
|
Sep 29 |
asked | Is it secure to use bcrypt-generated salt in cookie to serve as token in place of a password? |
