The problem is Fernet refers to a specific standard, if you change it, you've got something new and not interoperable :-)
Alex On Sat, May 28, 2016 at 12:25 AM, Todd Knarr <tkn...@silverglass.org> wrote: > On 05/27/2016 07:36 PM, Alex Gaynor wrote: > >> Fernet is a standard maintained outside pyca/cryptography, we wouldn't >> implement anything in Fernet that wasn't a part of that standard. >> > How about a version that left the Fernet class itself using AES128 but > added new classes that'd use AES192 and AES256? I can fork the code and use > my fork, but if I'm going to do the work anyway I'd like to feed it back in > for others to use if I can do that in an acceptable way. > > > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev@python.org > https://mail.python.org/mailman/listinfo/cryptography-dev > > -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: D1B3 ADC0 E023 8CA6
_______________________________________________ Cryptography-dev mailing list Cryptography-dev@python.org https://mail.python.org/mailman/listinfo/cryptography-dev
