From: Gaius <james.a.rosen@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: rack-contrib: add SHA-1 and SHA-2 to ETag
Date: Fri, 5 Feb 2010 17:11:14 -0800 (PST) [thread overview]
Message-ID: <64180f89-a4c4-4698-ae23-c43544f6a34d@f11g2000yqm.googlegroups.com> (raw)
I added support for SHA-1 and SHA-2 (-256, -384, and -512) digest
algorithms to ETag. The relevant commit is here:
http://github.com/jamesarosen/rack-contrib/commit/5f2aa98e5e3898b0e60f3adc4304330f1fa04e69
I admit that the primary benefit of SHA-2 (better resistance to pre-
and post-image attacks), is not terribly important in the context of
an ETag. Still, I prefer to avoid outdated hash functions where
possible.
next reply other threads:[~2010-02-06 1:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 1:11 Gaius [this message]
2010-02-08 18:36 ` rack-contrib: add SHA-1 and SHA-2 to ETag Ryan Tomayko
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=64180f89-a4c4-4698-ae23-c43544f6a34d@f11g2000yqm.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).