#28645: AuthenticationForm's inactive user error isn't raised when using
     Reporter:  Guilherme Junqueira  |                    Owner:
                                     |  shangdahao
         Type:  Bug                  |                   Status:  new
    Component:  contrib.auth         |                  Version:  1.11
     Severity:  Normal               |               Resolution:
     Keywords:  2.1                  |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0

Comment (by Tim Graham):

 That approach may leak whether or not a username exists because of the
 time it takes to hash a password. For user names that exist, password
 hashing will run twice compared to once for user names that don't exist.
 See #20760 for a past example.

Ticket URL: <https://code.djangoproject.com/ticket/28645#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to