diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2021-01-14 10:27:04 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2021-01-14 17:50:04 +0100 |
| commit | 0aa6a602b2b1cac6fe8e55051eed493b9cea7b81 (patch) | |
| tree | 172a55c26ec312e4988c40647632ecd9f866880f /docs/releases/3.1.txt | |
| parent | e7208f13c0448387e56c340eed46e1ed9ef9997e (diff) | |
Refs #31842 -- Removed DEFAULT_HASHING_ALGORITHM transitional setting.
Per deprecation timeline.
Diffstat (limited to 'docs/releases/3.1.txt')
| -rw-r--r-- | docs/releases/3.1.txt | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/releases/3.1.txt b/docs/releases/3.1.txt index 730d0b682a..e6c040f22e 100644 --- a/docs/releases/3.1.txt +++ b/docs/releases/3.1.txt @@ -101,17 +101,17 @@ of this release <deprecated-jsonfield>`. ``DEFAULT_HASHING_ALGORITHM`` settings -------------------------------------- -The new :setting:`DEFAULT_HASHING_ALGORITHM` transitional setting allows -specifying the default hashing algorithm to use for encoding cookies, password -reset tokens in the admin site, user sessions, and signatures created by +The new ``DEFAULT_HASHING_ALGORITHM`` transitional setting allows specifying +the default hashing algorithm to use for encoding cookies, password reset +tokens in the admin site, user sessions, and signatures created by :class:`django.core.signing.Signer` and :meth:`django.core.signing.dumps`. Support for SHA-256 was added in Django 3.1. If you are upgrading multiple instances of the same project to Django 3.1, you should set -:setting:`DEFAULT_HASHING_ALGORITHM` to ``'sha1'`` during the transition, in -order to allow compatibility with the older versions of Django. Note that this -requires Django 3.1.1+. Once the transition to 3.1 is complete you can stop -overriding :setting:`DEFAULT_HASHING_ALGORITHM`. +``DEFAULT_HASHING_ALGORITHM`` to ``'sha1'`` during the transition, in order to +allow compatibility with the older versions of Django. Note that this requires +Django 3.1.1+. Once the transition to 3.1 is complete you can stop overriding +``DEFAULT_HASHING_ALGORITHM``. This setting is deprecated as of this release, because support for tokens, cookies, sessions, and signatures that use SHA-1 algorithm will be removed in |