#36439: Auth hashing blocks event loop if using asyncio
-------------------------------------+-------------------------------------
     Reporter:  Robert Aistleitner   |                    Owner:  Roelzkie
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  contrib.auth         |                  Version:  5.2
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  async, auth,         |             Triage Stage:  Ready for
  asyncio, performance               |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):

 In [changeset:"9381e9ce1c0f353682c58203ed1b2ef3d7b77dfd" 9381e9ce]:
 {{{#!CommitTicketReference repository=""
 revision="9381e9ce1c0f353682c58203ed1b2ef3d7b77dfd"
 [6.1.x] Refs #36439 -- Added missing thread_sensitive=False to dummy
 password hasher path.

 The existing user path also uses thread_sensitive=False in
 acheck_password().

 Follow-up to 7f66c3b41f0fb0fb938d7b96e20a28dccdaa2ecd.

 Backport of 48e0a64e6491b464249086d6052a00c8d2be418e from main.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36439#comment:21>
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 visit 
https://groups.google.com/d/msgid/django-updates/0107019e88351389-4cbcce0f-ac3c-4bd1-bbb8-c864b1b75230-000000%40eu-central-1.amazonses.com.

Reply via email to