]> git.ozlabs.org Git - patchwork/commit
projects / patchwork / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 0deabd4) | patch
Don't just rely on random for UserPersonConfirmation keys
authorJeremy Kerr <jk@ozlabs.org>
Thu, 11 Sep 2008 06:42:26 +0000 (16:42 +1000)
committerJeremy Kerr <jk@ozlabs.org>
Thu, 11 Sep 2008 06:42:26 +0000 (16:42 +1000)
commita72679a9622db66e828e86377f29c9c0c6574d69
treecae300bb42b1806b09f28ae8251c5775778df760tree | snapshot (tar.gz zip)
parent0deabd4014cbc9419d203356786e966c4f803ea3commit | diff
Don't just rely on random for UserPersonConfirmation keys

It looks like we're getting identical keys generated for confirmation
keys. Problem has been reported to django, but in the meantime, salt
with the user and email details, then sha1 to give the final key.

This requires an increase in the field size for key, migration script
included.

Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
apps/patchwork/models.py diff | blob | history
lib/sql/migration/002-extend-userpersonconfirmation-key-length.sql [new file with mode: 0644] blob
web-based patch-tracking system