This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author christian.heimes
Recipients asvetlov, brandon-rhodes, christian.heimes, giampaolo.rodola, jcea, kristjan.jonsson, pitrou
Date 2013-06-27.09:54:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372326862.6.0.410016559941.issue16487@psf.upfronthosting.co.za>
In-reply-to
Content
I found two places:

if (ERR_GET_REASON(err) == X509_R_CERT_ALREADY_IN_HASH_TABLE) {
if (ERR_GET_REASON(err) == PEM_R_BAD_BASE64_DECODE)


AFAIK the _ssl module only supports PEM certs for loading. On the other hands cert data can only be retrieved as dict representation or binary DER data, e.g. getpeercert(binary_form=True) -> DER bytes. It's a bit of a puzzle to me.

It feels a bit strange to treat PEM certs as binary data, especially since the SSL module treats PEM as ASCII unicode. For example DER_cert_to_PEM_cert() accepts bytes and returns str, PEM_cert_to_DER_cert() converts str to bytes.
History
Date User Action Args
2013-06-27 09:54:22christian.heimessetrecipients: + christian.heimes, jcea, pitrou, kristjan.jonsson, giampaolo.rodola, asvetlov, brandon-rhodes
2013-06-27 09:54:22christian.heimessetmessageid: <1372326862.6.0.410016559941.issue16487@psf.upfronthosting.co.za>
2013-06-27 09:54:22christian.heimeslinkissue16487 messages
2013-06-27 09:54:22christian.heimescreate