network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 9 months |
| seen | Sep 20 '12 at 1:16 | |
| stats | profile views | 1 |
|
Sep 20 |
awarded | Scholar |
|
Sep 20 |
accepted | A Secure Cookie Protocol |
|
Sep 20 |
comment |
A Secure Cookie Protocol So you suggest to just generate random value, use it as a key to userID, and on each request get userID from server, thought if this is vulnerable to replay attack (and it seems to me it is) isnt secure cookie protocol batter approach as I dont need to store data on server which makes application a lot faster. |
|
Sep 20 |
awarded | Student |
|
Sep 19 |
asked | A Secure Cookie Protocol |
