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

Comment (by Tim Graham <timograham@…>):

 In [changeset:"57b95fedad5e0b83fc9c81466b7d1751c6427aae" 57b95fed]:
 {{{
 #!CommitTicketReference repository=""
 revision="57b95fedad5e0b83fc9c81466b7d1751c6427aae"
 [1.11.x] Fixed CVE-2018-6188 -- Fixed information leakage in
 AuthenticationForm.

 Reverted 359370a8b8ca0efe99b1d4630b291ec060b69225 (refs #28645).

 This is a security fix.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/28645#comment:11>
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 
https://groups.google.com/d/msgid/django-updates/068.a47f0536e4ff6943bc76da938006a301%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to