diff options
| author | Sascha Peilicke <saschpe@suse.de> | 2012-06-21 13:20:12 +0200 |
|---|---|---|
| committer | Sascha Peilicke <saschpe@suse.de> | 2012-07-03 10:18:56 +0200 |
| commit | 9aa2dda073b455e73d14c212cebb637ef6c4cab5 (patch) | |
| tree | 28340a3d0e5e68a82037cf02d66f36020669cdf5 /tools | |
| parent | 8e8d5a75d538ad3300859fc3d59e7bdfd760129c (diff) | |
| download | tuskar-ui-9aa2dda073b455e73d14c212cebb637ef6c4cab5.tar.gz | |
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
Diffstat (limited to 'tools')
| -rw-r--r-- | tools/pip-requires | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/tools/pip-requires b/tools/pip-requires index 8a34ec24..3ffd0988 100644 --- a/tools/pip-requires +++ b/tools/pip-requires @@ -6,3 +6,6 @@ python-glanceclient python-keystoneclient python-novaclient pytz + +# Horizon Utility Requirements +lockfile # for SECURE_KEY generation |