#31757: Adjust default SECRET_KEY to use `dj::insecure` prefix and add matching
deployment system check.
-------------------------------------+-------------------------------------
Reporter: Carlton Gibson | Owner: kosc
Type: New feature | Status: closed
Component: Core (System | Version: master
checks) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"b7f500396e05cd1f0bb8901fce16e2d8393d2779" b7f5003]:
{{{
#!CommitTicketReference repository=""
revision="b7f500396e05cd1f0bb8901fce16e2d8393d2779"
Fixed #31757 -- Adjusted system check for SECRET_KEY to warn about
autogenerated default keys.
Thanks Nick Pope, René Fleschenberg, and Carlton Gibson for reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31757#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.36a10e411259e1bdbfe2c37ede300bb8%40djangoproject.com.
