News for hackers. Stuff that matters.
Re:WebServerUid: Easy Unique Browser IDs for Rails by jcampbell1 on Monday February 24, 2014 @03:57PM (#7293388)
This is a good technique to know. I feel like that cookie should be HTTP only though. It looks like nginx doesn't support that out of the box.
Re:WebServerUid: Easy Unique Browser IDs for Rails by geweke on Monday February 24, 2014 @04:11PM (#7293439)
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... ;)

Re:WebServerUid: Easy Unique Browser IDs for Rails by jcampbell1 on Monday February 24, 2014 @05:43PM (#7293920)
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.

Re:WebServerUid: Easy Unique Browser IDs for Rails by geweke on Monday February 24, 2014 @06:33PM (#7294127)
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 by jcampbell1 on Monday February 24, 2014 @10:20PM (#7295176)
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.