Fernet is a standard maintained outside pyca/cryptography, we wouldn't implement anything in Fernet that wasn't a part of that standard.
The standard itself is in something of a hybernation state ATM, so candidly I don't know how receptive they'd be to such a proposed change. I fear your best option is probably to fork the Fernet mdoule, which thankfully isn't terribly much code. Alex On Fri, May 27, 2016 at 10:28 PM, Todd Knarr <tkn...@silverglass.org> wrote: > Would there be an interest in, or philosophical/design objections to, a > patch to allow Fernet to use AES192 and AES256 encryption? I've got a > situation where Fernet would be a good fit but 256-bit encryption is highly > desired. > > > > _______________________________________________ > 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
