-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not using SNI #5
Comments
@davidben I haven't had a chance to test this yet, hence the lack of PR |
Now tested to the extent that |
Ah, okay. :-) I also got confirmation that your patch fixed someone's offlineimap issue. |
Any luck? |
(Oops, missed that you already opened a PR.) |
Guys, it seems like we've run into a bit of a conundrum: Judging from the commit log, imaplib2 is completely abandoned, with the last commit being a year ago... |
Fixes jazzband/imaplib2#5 Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
This is starting to become a bigger issue, since OpenSSL 1.1.1 has now been backported to Ubuntu 18.04. Is there anyone who can help us get PR #6 merged and into Python patch releases? :-) |
Please, read this comment. |
Using the latest openssl (version 1.1.1), which supports TLS 1.3, imaplib2 fails to connect to (at least) GMail:
This is because imaplib2 does not support SNI, and Google returns an invalid certificate in that case. Copying from here:
Forcing TLS 1.2 works as expected:
The text was updated successfully, but these errors were encountered: