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 vstinner
Recipients christian.heimes, pitrou, vstinner
Date 2017-04-27.14:04:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493301874.63.0.247784920883.issue30175@psf.upfronthosting.co.za>
In-reply-to
Content
>  I suggest simply skipping the test, unless we find a remote IMAP server that accepts random TLS certs.

I tried "imap.gmail.com" server: first, it fails with:

imaplib.IMAP4.error: b'[AUTHENTICATIONFAILED] Invalid credentials (Failure)'

And then:

imaplib.IMAP4.error: b'[ALERT] Web login required: https://support.google.com/mail/answer/78754 (Failure)'

Well, I don't see why an IMAP server would accept our client cert?

Lib/test/keycert3.pem was added by the commit 58ddc9d743d09ee93d5cf46a4de62eab30dad79d (made by Antoine Pitrou): the certificated was *generated* randomly by Lib/test/make_ssl_certs.py (also added by the same commit).

RemoteIMAP_SSLTest was added by commit b1436f185dac249f0f6dc342b2a543ae2d1db63d (Antoine Pitrou) in 2010 with the server: cyrus.andrew.cmu.edu.

So since 2010 until a few days ago, cyrus.andrew.cmu.edu accepted random client certificate, but now the server started to fail... as expected?
History
Date User Action Args
2017-04-27 14:04:34vstinnersetrecipients: + vstinner, pitrou, christian.heimes
2017-04-27 14:04:34vstinnersetmessageid: <1493301874.63.0.247784920883.issue30175@psf.upfronthosting.co.za>
2017-04-27 14:04:34vstinnerlinkissue30175 messages
2017-04-27 14:04:34vstinnercreate