diff options
| author | Tim Graham <timograham@gmail.com> | 2013-10-17 18:58:24 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-10-17 18:58:24 -0400 |
| commit | d97bec5ee3a6284d30b613c9070588a60358e7ec (patch) | |
| tree | 217cfe68ca000cdc34e7eb33a4fc3b5bb60981fc | |
| parent | 7e5d7a76bf60564d39d25a101380e47da7f1e2f6 (diff) | |
Removed 1.6 release note text regarding password limit length.
This changed was reverted in 5d74853e156105ea02a41f4731346dbe272c2412.
| -rw-r--r-- | docs/releases/1.6.txt | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt index 0f52f224ce..a3b40aec28 100644 --- a/docs/releases/1.6.txt +++ b/docs/releases/1.6.txt @@ -810,22 +810,6 @@ as JSON requires string keys, you will likely run into problems if you are using non-string keys in ``request.session``. See the :ref:`session_serialization` documentation for more details. -4096-byte limit on passwords -~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -.. note:: - This behavior was also added in the Django 1.5.4 and 1.4.8 security - releases. - -Historically, Django has imposed no length limit on plaintext -passwords. This enables a denial-of-service attack through submission -of bogus but extremely large passwords, tying up server resources -performing the (expensive, and increasingly expensive with the length -of the password) calculation of the corresponding hash. - -Django now imposes a 4096-byte limit on password length, and will fail -authentication with any submitted password of greater length. - Miscellaneous ~~~~~~~~~~~~~ |