AuthenticationForm.is_valid after validation should reset password field for security reason

[Robert Lujo]

When you use django.contrib.auth.views.login for login procedure it works like classic form:

• GET - creates empty AuthenticationForm object
• POST - validates usr/pwd against auth backend
• POST - if ok then you're being logged in and redirected to somewhere
• POST - if not ok - then you're again on the same page with information that credentials are not ok, and the form is already filled with username and password which you typed in on the page before.

In last case (POST FAIL) the password travels client->server->client. I think the last server->client travel is not needed and can be treated as security issue. Why to pre-fill the password field when it is false anyway, and why to expose password over the network twice, when it could be exposed only once. I didn't had time to investigate how to solve this exactly, but my suggestion is to do work on the AuthenticationForm.is_valid overridden method (can be seen in diff file I attach). Diff is against r1105.

[Robert Lujo]

Place where fix the problem

[Chris Beaven]

Here's the correct fix...

[kc9ddi]

Would strongly encourage adopting the suggested type of behavior. Not only is it potentially more secure, but it seems to be the most common behavior in use for most login forms users encounter on the internet.

[Chris Beaven]

Hi kc9ddi,

If you want to promote tickets, the django-dev google group is a better place to do it.

[Robert Lujo]

Is this duplicate to #13316?

[Chris Beaven]

Fixed in [13498]