[Python-Dev] Hash collision security issue (now public) (original) (raw)
Tim Delaney timothy.c.delaney at gmail.com
Fri Dec 30 01:55:45 CET 2011
- Previous message: [Python-Dev] Hash collision security issue (now public)
- Next message: [Python-Dev] Hash collision security issue (now public)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 30 December 2011 06:59, Tim Delaney <timothy.c.delaney at gmail.com> wrote:
+0 to exposing the salt as a constant (3.3+ only) - or alternatively expose a hash function that just takes an existing hash and returns the salted hash. That would make it very easy for anything that wanted a salted hash to get one.
Sorry - brain fart on my part there - the salt needs to be included right from the start.
Tim Delaney -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20111230/fed6ebb5/attachment.html>
- Previous message: [Python-Dev] Hash collision security issue (now public)
- Next message: [Python-Dev] Hash collision security issue (now public)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]