Right, that backwards compatibility issue seems quite difficult to solve, although if the worst thing to happen is that all users are logged out, it shouldn't be that bad. Will read the ticket in detail.
El martes, 8 de mayo de 2018, 20:31:28 (UTC-3), Tim Graham escribió: > > There's a ticket about it: https://code.djangoproject.com/ticket/27468 > > Backwards compatibility is the main consideration. > > On Tuesday, May 8, 2018 at 6:44:05 PM UTC-4, Cristiano Coelho wrote: >> >> Looks like the Signer class (and perhaps other parts of the code) still >> use SHA1 ([1] and [2]) for the HMAC signing/hashing process. >> >> I'm wondering if there's any specific reason to use SHA1 over newer >> versions, or if it would be worth it to pass the hash algorithm as a >> variable or even config option. >> >> >> >> [1] >> https://github.com/django/django/blob/master/django/core/signing.py#L45 >> [2] >> https://github.com/django/django/blob/master/django/utils/crypto.py#L23 >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6cdfdeca-e8f1-4cda-8c28-f623136e88be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
