From 0265b1b49ba10f957abfd1311d0bae0ecefc3111 Mon Sep 17 00:00:00 2001 From: fschwebel Date: Mon, 30 Jan 2023 08:31:39 +0100 Subject: [PATCH] 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. --- docs/topics/auth/passwords.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/auth/passwords.txt b/docs/topics/auth/passwords.txt index 57053c1a2a..eb3b06b65e 100644 --- a/docs/topics/auth/passwords.txt +++ b/docs/topics/auth/passwords.txt @@ -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.