From 9aa2dda073b455e73d14c212cebb637ef6c4cab5 Mon Sep 17 00:00:00 2001 From: Sascha Peilicke Date: Thu, 21 Jun 2012 13:20:12 +0200 Subject: Provide utilities to automate secure secret key generation Implements blueprint automatic-secure-key-generation Reduce the likeliness that the (commented-out) default key is abused and document possible options instead. Also use a non-empty SECRET_KEY for development / testing environments. A later patch would make it a hard error if no SECRET_KEY is defined (i.e. Django defaults to an empty string which is anything but secure). Unfortunately, I can't do it now as the devstack integration test would fail (they don't set a SECRET_KEY either) currently. So, when this blueprint is accepted, I would submit a fix to devstack and afterwards add the error message to warn the user about insecure defaults. Addressed PEP-8 issues Change-Id: Ifdab8e6b6fb3025fde7a2b92beb046ec9c5cba7f --- .gitignore | 1 + 1 file changed, 1 insertion(+) (limited to '.gitignore') diff --git a/.gitignore b/.gitignore index 3fedf1d0e..d353785ec 100644 --- a/.gitignore +++ b/.gitignore @@ -12,6 +12,7 @@ pylint.txt reports horizon.egg-info openstack_dashboard/local/local_settings.py +openstack_dashboard/test/.secret_key_store doc/build/ doc/source/sourcecode /static/ -- cgit v1.2.1