2015-01-03 18:27:08 +00:00
|
|
|
==========================
|
|
|
|
Django 1.7.3 release notes
|
|
|
|
==========================
|
|
|
|
|
|
|
|
*Under development*
|
|
|
|
|
2014-11-25 22:06:31 +00:00
|
|
|
Django 1.7.3 fixes several security issues and bugs in 1.7.2.
|
2015-01-03 18:27:08 +00:00
|
|
|
|
2014-09-10 17:06:19 +00:00
|
|
|
WSGI header spoofing via underscore/dash conflation
|
|
|
|
===================================================
|
|
|
|
|
|
|
|
When HTTP headers are placed into the WSGI environ, they are normalized by
|
|
|
|
converting to uppercase, converting all dashes to underscores, and prepending
|
|
|
|
`HTTP_`. For instance, a header ``X-Auth-User`` would become
|
|
|
|
``HTTP_X_AUTH_USER`` in the WSGI environ (and thus also in Django's
|
|
|
|
``request.META`` dictionary).
|
|
|
|
|
|
|
|
Unfortunately, this means that the WSGI environ cannot distinguish between
|
|
|
|
headers containing dashes and headers containing underscores: ``X-Auth-User``
|
|
|
|
and ``X-Auth_User`` both become ``HTTP_X_AUTH_USER``. This means that if a
|
|
|
|
header is used in a security-sensitive way (for instance, passing
|
|
|
|
authentication information along from a front-end proxy), even if the proxy
|
|
|
|
carefully strips any incoming value for ``X-Auth-User``, an attacker may be
|
|
|
|
able to provide an ``X-Auth_User`` header (with underscore) and bypass this
|
|
|
|
protection.
|
|
|
|
|
|
|
|
In order to prevent such attacks, both Nginx and Apache 2.4+ strip all headers
|
|
|
|
containing underscores from incoming requests by default. Django's built-in
|
|
|
|
development server now does the same. Django's development server is not
|
|
|
|
recommended for production use, but matching the behavior of common production
|
|
|
|
servers reduces the surface area for behavior changes during deployment.
|
2015-01-03 18:27:08 +00:00
|
|
|
|
|
|
|
Bugfixes
|
|
|
|
========
|
|
|
|
|
2015-01-05 15:55:48 +00:00
|
|
|
* The default iteration count for the PBKDF2 password hasher has been
|
|
|
|
increased by 25%. This part of the normal major release process was
|
|
|
|
inadvertently omitted in 1.7. This backwards compatible change will not
|
|
|
|
affect users who have subclassed
|
|
|
|
``django.contrib.auth.hashers.PBKDF2PasswordHasher`` to change the
|
|
|
|
default value.
|
2015-01-05 17:23:57 +00:00
|
|
|
|
|
|
|
* Fixed a crash in the CSRF middleware when handling non-ASCII referer header
|
|
|
|
(:ticket:`23815`).
|
2015-01-09 21:18:34 +00:00
|
|
|
|
|
|
|
* Fixed a crash in the ``django.contrib.auth.redirect_to_login`` view when
|
|
|
|
passing a :func:`~django.core.urlresolvers.reverse_lazy` result on Python 3
|
|
|
|
(:ticket:`24097`).
|
2015-01-09 22:05:58 +00:00
|
|
|
|
|
|
|
* Added correct formats for Greek (``el``) (:ticket:`23967`).
|
2015-01-10 14:18:06 +00:00
|
|
|
|
2015-01-10 23:30:47 +00:00
|
|
|
* Fixed a migration crash when unapplying a migration where multiple operations
|
|
|
|
interact with the same model (:ticket:`24110`).
|