[Idpy-discuss] Forks of Forks of PyCrypto and PyASN1 in pyXMLSecurity

31 juli 2018 kl. 13:40 skrev Steffen Klemer <klemer at dfn.de>: Hey list, is there a specific reason that pyXMLSecurity maintains forked, crippled down and slightly changed versions of pycrypto (abandoned) and PyASN1 (with security changes in the upstream since forking)? From a quick look it seems that it might be quiet easy to port it over to PyCryptodome(x) which is maintained and itself a fork of pycrypto and would bring back some speed optimized parts in c (that were cut away when forking) as well as ECC that might get relevant in the coming years. My main concern is about the long term security impact of a self-maintained crypto module; speed is just a nice addition ;). pkcs11 wouldn't be impacted by it and has to be kept separately. Would patches/PR be welcome or just a waste of time? Steffen -- DFN-Verein Steffen Klemer Alexanderplatz 1 +49 30 884299 307 10178 Berlin klemer at dfn.de Fax: 030 88 42 99 370 http://www.dfn.de _______________________________________________ Idpy-discuss mailing list Idpy-discuss at lists.sunet.se https://lists.sunet.se/listinfo/idpy-discuss