9aa2dda073
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
26 lines
323 B
Plaintext
26 lines
323 B
Plaintext
*.pyc
|
|
*.swp
|
|
.environment_version
|
|
.selenium_log
|
|
.coverage*
|
|
.noseids
|
|
.DS_STORE
|
|
coverage.xml
|
|
nosetests.xml
|
|
pep8.txt
|
|
pylint.txt
|
|
reports
|
|
horizon.egg-info
|
|
openstack_dashboard/local/local_settings.py
|
|
openstack_dashboard/test/.secret_key_store
|
|
doc/build/
|
|
doc/source/sourcecode
|
|
/static/
|
|
.venv
|
|
.tox
|
|
build
|
|
dist
|
|
AUTHORS
|
|
ChangeLog
|
|
tags
|