rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Christian von Kleist <cvonkleist@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: New encrypted_cookie gem: encrypted sessions for Rack
Date: Sat, 5 Mar 2011 15:18:57 -0800 (PST)	[thread overview]
Message-ID: <d0368673-949f-4852-a34d-6a43c50b487f@u6g2000vbh.googlegroups.com> (raw)

I've created a gem called encrypted_cookie which gives Rack encrypted,
integrity-protected session storage in cookies. (The integrity
protection is the same as the normal Rack::Session::Cookie, and the
added encryption is 128-bit AES).

I'd *really* appreciate feedback on the security of my implementation
from other Rack users. If you'd like to try it out, it's very easy to
use:

1) gem install encrypted_cookie
2) Then do this in your Rack app:

  require 'encrypted_cookie'

  use Rack::Session::EncryptedCookie,
    :secret => TYPE_YOUR_LONG_RANDOM_STRING_HERE

More information at https://github.com/cvonkleist/encrypted_cookie

Much thanks in advance to anyone who can comment on the security of
this approach!

                 reply	other threads:[~2011-03-06  0:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d0368673-949f-4852-a34d-6a43c50b487f@u6g2000vbh.googlegroups.com \
    --to=rack-devel@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).