3 ms·
> Using a secret to sign or encrypt a cookie does normally work If the secret key is not compromised. So you have to ask yourself - why you send to the user so
by smsm42 8y ago
> Using a secret to sign or encrypt a cookie does normally work
If the secret key is not compromised. So you have to ask yourself - why you send to the user some info that is so sensitive that needs signing? Why not just keep this info to yourself and send an opaque ID instead? Yes, I know there are issues with it too, but at least this issue is not there.
> 3 as well I think is unfair. That isn't something facebook implemented
I didn't say it's Facebook fault - though ultimately, of course, it is as much as if you run certain software on your servers and do not configure it properly, it's your fault. So there's a fail in having security key in a place that's so easily accessible that debug mode dumps it without even asking. Not necessarily a direct Facebook fail, but a fail.
- nijave 8y agoSee JWT. You can make stateless apps easier without worrying about a trip to the database to grab session info https://12factor.net/disposability https://12factor.net/disposability If you want disposability with the ID method you need some sort of datastore or cache to contain session info