On Sep 5, 2007, at 12:09 PM, Martin v. Löwis wrote: > That's for 2.5. In 3.0 (currently), hashlib requires OpenSSL.
On the wider subject of crypto in Python, is there someone who actively takes care of this area and who could clarify any legal/ export restrictions on what gets included with the source distribution? There's good-quality, suitably licensed crypto code out there implementing most of the major ciphers, hashes, and asymmetric cryptosystems. I'd love it if we included a real set of crypto batteries with 3.0 that didn't depend on outside libraries, and provided more than just a hash or two. Doing the work isn't a problem. Is legalese? -- Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
