full-disclosure - Re: [Ruby on Rails] Move away from CookieStore if you care about your users and their security. Here is a technical explanation why.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130925133610.GO3522@sentinelchicken.org>
Date: Wed, 25 Sep 2013 06:36:10 -0700
From: Tim <tim-security@...tinelchicken.org>
To: "G. S. McNamara" <main@...cnamara.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: [Ruby on Rails] Move away from CookieStore if
 you care about your users and their security. Here is a technical
 explanation why.

> 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/