[Python-Dev] Python 2.6 and 3.0 ...and applink.c?
Bugbee, Larry
larry.bugbee at boeing.com
Tue Feb 26 19:54:55 CET 2008
More information about the Python-Dev mailing list
Tue Feb 26 19:54:55 CET 2008
- Previous message: [Python-Dev] Python 2.6 and 3.0 ...and applink.c?
- Next message: [Python-Dev] Getting a second review on a rewrite of test_logging
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I appreciate the gesture but... At this juncture I'd prefer to see OpenSSL access to crypto APIs remain an external library like M2Crypto, at least until the Python community is willing to do a full implementation of all OpenSSL APIs. ...and maintain it. Larry -----Original Message----- From: Bill Janssen [mailto:janssen at parc.com] Sent: Tuesday, February 26, 2008 10:14 AM To: Bugbee, Larry Cc: Christian Heimes; python-dev at python.org Subject: Re: [Python-Dev] Python 2.6 and 3.0 ...and applink.c? > I personally have not used _ssl but on quick inspection I don't see > any of the crypto algorithms implemented, AES, ECDSA, etc. What if we > want to encrypt or sign content using OpenSSL? I suggested adding a class which gives you access to those. I think it's a good idea, and that serious use of SSL will require signing eventually. If you'd like to submit an RFE, particularly an RFE with a patch which includes a test case, that would move things along smartly. Bill
- Previous message: [Python-Dev] Python 2.6 and 3.0 ...and applink.c?
- Next message: [Python-Dev] Getting a second review on a rewrite of test_logging
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list