Sascha Peilicke 9aa2dda073 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		2012-07-03 10:18:56 +02:00
..
install_venv.py	Add distribute to test-requires.	2012-04-18 07:39:27 -07:00
pip-requires	Provide utilities to automate secure secret key generation	2012-07-03 10:18:56 +02:00
rfc.sh	Remove trailing whitespaces in regular file	2012-03-03 12:31:19 +08:00
test-requires	Corrections for stricter pep8 checking.	2012-06-23 13:16:37 -07:00
with_venv.sh	Rename venvs to match everyone else.	2012-02-13 12:11:08 -08:00