#9687: Use more randomness in secret key generation
-----------------------------------------+----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: closed | Milestone:
Component: Core framework | Version: 1.0
Resolution: wontfix | Keywords: SECRET_KEY random
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------+----------------------------------
Comment (by [EMAIL PROTECTED]):
Whatever.
The issue shouldn't be whether it's "good enough", the issue should be
whether it improves things. You've got someone else not only noticing a
problem, but actually supplying you with source code, and it's not
acceptable simply because the current system meets your own standards for
'fitness'.
I could point to [http://code.djangoproject.com/ticket/1180] as an example
of the "works for me" approach breaking, as well as being an example of
Django developers not really getting basic cryptographic randomness
issues, but then I'd get accused of being petty.
The question of whether your accepting reasonable patches or not is your
own problem.
--
Ticket URL: <http://code.djangoproject.com/ticket/9687#comment:2>
Django <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
