mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-06-10 14:09:14 +00:00
Code Issues 32 Releases Wiki Activity

[3.1.x] Refs #31864 -- Doc'd that DEFAULT_HASHING_ALGORITHM requires 3.1.1+ in release notes.

Browse Source 
Backport of b2b0711b555fa292751763c2df4fe577c396f265 from master
This commit is contained in:
Uri 2020-08-08 08:05:38 +03:00 committed by Carlton Gibson
parent c21bbe0883
commit cdfdbb3411
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/releases/3.1.txt
View File

@ -109,9 +109,9 @@ reset tokens in the admin site, user sessions, and signatures created by
Support for SHA-256 was added in Django 3.1. If you are upgrading multiple 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 instances of the same project to Django 3.1, you should set
:setting:`DEFAULT_HASHING_ALGORITHM` to ``'sha1'`` during the transition, in :setting:`DEFAULT_HASHING_ALGORITHM` to ``'sha1'`` during the transition, in
order to allow compatibility with the older versions of Django. Once the order to allow compatibility with the older versions of Django. Note that this
transition to 3.1 is complete you can stop overriding requires Django 3.1.1+. Once the transition to 3.1 is complete you can stop
:setting:`DEFAULT_HASHING_ALGORITHM`. overriding :setting:`DEFAULT_HASHING_ALGORITHM`.
This setting is deprecated as of this release, because support for tokens, 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 cookies, sessions, and signatures that use SHA-1 algorithm will be removed in