diff options
| author | Jiang Haiyun <jiang.haiyun@gmail.com> | 2016-07-04 23:02:11 +0800 |
|---|---|---|
| committer | Simon Charette <charette.s@gmail.com> | 2016-07-04 11:04:14 -0400 |
| commit | 0b57016ec7f7faf53b791c33c2ec6d04e92d23a3 (patch) | |
| tree | ae3ac13039456c1f7f8df62dbf1a01047329d49a | |
| parent | 04beab3399fed99ccb21d0e684df52de6f99cc2c (diff) | |
[1.9.x] Fixed a typo in auth docs.
Backport of 6d61ec0e1a4eb5768be5add9e1c44c89dacbfa7e from master
| -rw-r--r-- | docs/topics/auth/passwords.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/auth/passwords.txt b/docs/topics/auth/passwords.txt index 5b88ce33dd..2856e7bdb0 100644 --- a/docs/topics/auth/passwords.txt +++ b/docs/topics/auth/passwords.txt @@ -113,7 +113,7 @@ algorithm. that ``bcrypt(password_with_100_chars) == bcrypt(password_with_100_chars[:72])``. The original ``BCryptPasswordHasher`` does not have any special handling and thus is also subject to this hidden password length limit. - ``BCryptSHA256PasswordHasher`` fixes this by first first hashing the + ``BCryptSHA256PasswordHasher`` fixes this by first hashing the password using sha256. This prevents the password truncation and so should be preferred over the ``BCryptPasswordHasher``. The practical ramification of this truncation is pretty marginal as the average user does not have a |
