#31807: Whether support more secure method to generate session id
----------------------------------+--------------------------------------
     Reporter:  dotuser           |                    Owner:  nobody
         Type:  New feature       |                   Status:  closed
    Component:  contrib.sessions  |                  Version:  2.2
     Severity:  Normal            |               Resolution:  wontfix
     Keywords:                    |             Triage Stage:  Unreviewed
    Has patch:  0                 |      Needs documentation:  0
  Needs tests:  0                 |  Patch needs improvement:  0
Easy pickings:  0                 |                    UI/UX:  0
----------------------------------+--------------------------------------

Comment (by felixxm):

 > `secrets` doesn't change any behavior or add security for now[1][2].

 Yes I know, but do we need more? Session keys have 32 chars, so =~ 165
 bits.

 > So, for security or cryptographic use case in session id, any others
 plan to support a more secure method?

 Do you have any proposition?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31807#comment:3>
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/065.556c41f614edec1021fcc4fb36c37369%40djangoproject.com.

Reply via email to