Sorry, I explained poorly. We do upgrade passwords when the iteration count is increased https://docs.djangoproject.com/en/1.8/topics/auth/passwords/#password-upgrading
If we increase the iterations to <new iterations>, when a user logs in, we have to hash <current iterations> to check the password against the current hash plus <new iterations> to store the upgraded password. If pbkdf2 is slow, isn't it reasonable that this could cause a CPU spike on a high traffic site? On Tuesday, September 22, 2015 at 1:39:12 PM UTC-4, Xof wrote: > > > On Sep 22, 2015, at 10:27 AM, Tim Graham <timog...@gmail.com <javascript:>> > wrote: > > > We have access to the plain text password when the user logs in. > > Right, so we could *in theory* upgrade the user's password then if we > wished (not clear if we want to). Even so, I don't think that would be a > DDoS-attack level problem, since it's no worse than a user resetting their > password. > > -- > -- Christophe Pettus > x...@thebuild.com <javascript:> > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/bd8df6d7-4355-427e-83b4-024482e2fdf0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
