Live data from Hacker News

WebServerUid: Easy Unique Browser IDs for Rails

swiftype.com

11–12 of 12 posts

Re: WebServerUid: Easy Unique Browser IDs for Rails

#11
post #5

Earlier quoted context omitted.

Really good point. Even better, I'd really like these cookies to be digitally signed (like Rails' session cookies are by default), so that they're unforgeable. Seems like it wouldn't be too terribly hard to add to nginx...hmm... ;)

They should be secure random strings, no need to sign. BTW, rails signed session cookies are terrible from a security perspective. Thank god Github has moved away from them.

What, in particular, is problematic about them? Do you mean their particular implementation, the fact that they aren't also encrypted, or the general "password equivalent in a cookie" concept overall?

Re: WebServerUid: Easy Unique Browser IDs for Rails

#12
post #11

Earlier quoted context omitted.

They should be secure random strings, no need to sign. BTW, rails signed session cookies are terrible from a security perspective. Thank god Github has moved away from them.

What, in particular, is problematic about them? Do you mean their particular implementation, the fact that they aren't also encrypted, or the general "password equivalent in a cookie" concept overall?

Yeah, the one ring to rule them all problem. One bad employee, or one of the many rails zero-day issues, potentially compromises the site indefinitely for all eternity.
Post reply on HN