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  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]
Date: Wed, 25 Sep 2013 06:36:10 -0700
From: Tim <>
To: "G. S. McNamara" <>
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).


Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia -

Powered by blists - more mailing lists