#24465: Failed logins are recorded as HTTP 200 instead of HTTP 403 -------------------------------+-------------------------------------- Reporter: marklit | Owner: nobody Type: Bug | Status: closed Component: contrib.admin | Version: 1.7 Severity: Normal | Resolution: invalid Keywords: | Triage Stage: Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------+--------------------------------------
Comment (by marklit): My concern is that this gives a chance to run a dictionary attack against the login. If fail2ban is monitoring nginx's logs or django's logs directly the response for a failed login and a correct one look the same. -- Ticket URL: <https://code.djangoproject.com/ticket/24465#comment:3> 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/065.2bb2eaf9461b2d1cab1a18a324c137a7%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.