Full Disclosure mailing list archives
Re: [Ruby on Rails] Move away from CookieStore if you care about your users and their security. Here is a technical explanation why.
From: Tim <tim-security () sentinelchicken org>
Date: Wed, 25 Sep 2013 06:36:10 -0700
The fix is to configure your Rails app to store most session information on the server side in the database. Move away from the default CookieStore, which stores the entire session hash in the cookie, to something like ActiveRecordStore.
It seems to me that a simple fix to the CookieStore would be to add a time stamp to the serialized (and signed) data. Then an expiration time frame could easily be enforced. In general, stateless cookies like this have great advantages. They just need to be implemented correctly (which is admittedly tricky). tim _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Current thread:
- [Ruby on Rails] Move away from CookieStore if you care about your users and their security. Here is a technical explanation why. G. S. McNamara (Sep 25)
- Re: [Ruby on Rails] Move away from CookieStore if you care about your users and their security. Here is a technical explanation why. joernchen (Sep 25)
- Re: [Ruby on Rails] Move away from CookieStore if you care about your users and their security. Here is a technical explanation why. Tim (Sep 25)
