Fixed typo in docs/topics/auth/passwords.txt.

Wrapped hashing is only possible if the inner wrapped function is the
same as the previous hasher.
This commit is contained in:
fschwebel 2023-01-30 08:31:39 +01:00 committed by GitHub
parent 8acc433e41
commit 0265b1b49b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions

View File

@ -336,7 +336,7 @@ to happen when a user logs in (which may never happen if a user doesn't return
to your site). In this case, you can use a "wrapped" password hasher.
For this example, we'll migrate a collection of MD5 hashes to use
PBKDF2(SHA1(password)) and add the corresponding password hasher for checking
PBKDF2(MD5(password)) and add the corresponding password hasher for checking
if a user entered the correct password on login. We assume we're using the
built-in ``User`` model and that our project has an ``accounts`` app. You can
modify the pattern to work with any algorithm or with a custom user model.