On Sun, 2016-06-12 at 23:51 -0400, Paul Kehrer wrote: > In general I'm in favor of pulling jwcrypto (or something like it) > into cryptography. The obstacles are going to be figuring out the > licensing (cryptography is Apache2/BSD dual licensed and any code > contributed to it needs to be available under those licenses), > discussing what (if any) API changes need to be made to fit in with > the API design of the hazmat layer, and general "make the code style > match cryptography".
Jwcrypto author here, from my POV we can discuss license/API/style adjustments needed, just let me know in which form you want to have this discussion. Simo. -- Simo Sorce * Red Hat, Inc * New York _______________________________________________ Cryptography-dev mailing list Cryptography-dev@python.org https://mail.python.org/mailman/listinfo/cryptography-dev
