mirror of
https://github.com/retspen/webvirtcloud
synced 2026-11-08 19:26:48 +00:00
405e6f1445
The admin page that creates a user saved the form first, which wrote the user with the raw password in the password column, and hashed it with a second save afterwards. The raw password was in the database, and in its journal and any copy taken meanwhile, and stayed there if anything failed between the two writes. - UserCreateForm hashes the password before the first save; groups and permissions are saved as before. - The form applies AUTH_PASSWORD_VALIDATORS, after the user fields are set (so the similarity check sees the new username), as the password change forms already did. The settings template configures no validators, so nothing changes unless an installation sets them. The tests record the SQL parameters of the request: the previous code wrote the raw password in the INSERT; it also accepted passwords that configured validators reject. |
||
|---|---|---|
| .. | ||
| migrations | ||
| templates/admin | ||
| __init__.py | ||
| apps.py | ||
| decorators.py | ||
| forms.py | ||
| models.py | ||
| permissions.py | ||
| test_user_create.py | ||
| tests.py | ||
| urls.py | ||
| views.py | ||