summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCarl Meyer <carl@oddbird.net>2012-03-02 04:04:56 +0000
committerCarl Meyer <carl@oddbird.net>2012-03-02 04:04:56 +0000
commit60119d4f49f78a635f801d53c102f1463e28fe8a (patch)
treef617f0e93b36974d5e92b172917b931af25ed37e /docs
parent10e671efaa824e5614ceb79356f0bf59ebb58c4d (diff)
Refs #17800 - Added release notes and deprecation note about SECRET_KEY requirement.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17617 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/internals/deprecation.txt4
-rw-r--r--docs/releases/1.4.txt16
2 files changed, 20 insertions, 0 deletions
diff --git a/docs/internals/deprecation.txt b/docs/internals/deprecation.txt
index 16dbec8e1d..cb91a1c0a3 100644
--- a/docs/internals/deprecation.txt
+++ b/docs/internals/deprecation.txt
@@ -124,6 +124,10 @@ these changes.
See the :doc:`Django 1.3 release notes</releases/1.3>` for more details on
these changes.
+* Starting Django without a :setting:`SECRET_KEY` will result in an exception
+ rather than a `DeprecationWarning`. (This is accelerated from the usual
+ deprecation path; see the :doc:`Django 1.4 release notes</releases/1.4>`.)
+
* The ``mod_python`` request handler will be removed. The ``mod_wsgi``
handler should be used instead.
diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt
index 7b45f9e4e2..cce28d8c78 100644
--- a/docs/releases/1.4.txt
+++ b/docs/releases/1.4.txt
@@ -617,6 +617,21 @@ Django 1.4 also includes several smaller improvements worth noting:
Backwards incompatible changes in 1.4
=====================================
+SECRET_KEY setting is required
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Running Django with an empty or known :setting:`SECRET_KEY` disables many of
+Django's security protections, and can lead to remote-code-execution
+vulnerabilities; no Django site should ever be run without a
+:setting:`SECRET_KEY`.
+
+In Django 1.4, starting Django with an empty :setting:`SECRET_KEY` will raise a
+`DeprecationWarning`. In Django 1.5, it will raise an exception and Django will
+refuse to start. This is slightly accelerated from the usual deprecation path
+due to the severity of the consequences of running Django with no
+:setting:`SECRET_KEY`.
+
+
django.contrib.admin
~~~~~~~~~~~~~~~~~~~~
@@ -756,6 +771,7 @@ instance:
* Time period: The amount of time you expect user to take filling out
such forms.
+
django.contrib.flatpages
~~~~~~~~~~~~~~~~~~~~~~~~