My proposal is to add a django-admin.py command or manage.py command which
generates a new SECRET_KEY in order to improve safety.
Sometimes I copy projects. I'd like to change the SECRET_KEY then. As far
as I know, there is no (documented) way to generate a new SECRET_KEY,
except for creating a new online project and copying that key.
Or I could implement a random function myself (which might be actually
worse implemented then django's default key generation), or I could use
the first Google hit to generate a key over an insecure connection. Both
raise my safety concerns.
--
Ticket URL: <https://code.djangoproject.com/ticket/24448>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* easy: 0 => 1
* needs_docs: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/24448#comment:1>
* status: new => closed
* resolution: => wontfix
Comment:
I don't see this as something Django needs to provide. My understanding is
that any random string is fine. There are online generators that use
https. I'm averse to adding management commands for every little task as
there are overheads for code, docs, and tests. If someone has stronger
arguments, please reopen or use the DevelopersMailingList for discussion.
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/24448#comment:2>
--
Ticket URL: <https://code.djangoproject.com/ticket/24448#comment:3>