No, it won't move the problem to 3.2. The problem is that 3.0 only knows about sha1. 3.1 and later know about sha1 and sha256. Meaning, any >=3.1,<4.0 version can decode and verify signed data from 4.0 and before.
Cheers Markus On Fri, Jul 31, 2020, at 12:08 PM, Raffaele Salmaso wrote: > On Fri, Jul 31, 2020 at 11:47 AM Carlton Gibson > <carlton.gib...@gmail.com> wrote: > > Add the new setting default to sha1. > > Raise a DeprecationWarning unless it’s set to sha256 (so folks can opt-in > > to the future.) > > Remove setting, and change default to sha256, when 4.0? > > > > Does that sound right? (Grrr.) > I think this just move the migration problem from 3.2 to 4.0. > What about the other way: add a migration setting set to new algorithm, > so who really need sha1 can opt-in to old algorithm? > > -- > | Raffaele Salmaso > | https://salmaso.org > | https://bitbucket.org/rsalmaso > | https://github.com/rsalmaso > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CABgH4Jt0xXzXrFO8vAFFbF_zabF6xhFGnnTS1rJi_iWAT9fJRg%40mail.gmail.com > > <https://groups.google.com/d/msgid/django-developers/CABgH4Jt0xXzXrFO8vAFFbF_zabF6xhFGnnTS1rJi_iWAT9fJRg%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1b35a40d-c3e3-4aab-a856-078f2efad7c4%40beta.fastmail.com.
