classification
Title: imap breaks on OpenSSL 1.1.1 when SNI is enforced
Type: behavior Stage: resolved
Components: SSL Versions: Python 2.7
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: christian.heimes Nosy List: alex, cfactoid, christian.heimes, dstufft, janssen
Priority: normal Keywords:

Created on 2019-08-06 19:49 by cfactoid, last changed 2019-08-06 21:49 by cfactoid. This issue is now closed.

Messages (2)
msg349131 - (view) Author: Casey (cfactoid) * Date: 2019-08-06 19:49
OpenSSL 1.1.1 is an LTS release that will see long maintenance, and Ubuntu 18.04 LTS has now upgraded from 1.1.0 to 1.1.1. However, with this upgrade, TLS 1.3 allows email clients to require an SNI for the handshake to succeed. Because the 2.7 imap module does not enforce or provide SNI to the handshake, Python 2.7 with OpenSSL 1.1.1 will break if an email client requires the SNI hostname.

Relevant 2.7 file:
https://github.com/python/cpython/blob/2.7/Lib/imaplib.py

Right now, the only email client that enforces an SNI header to connect is GMail, and this is why no SSL or imap tests would currently fail due to this issue. This issue was addressed in Python 3.4 but not backported as far as I've been able to tell:

https://github.com/python/cpython/commit/7243b574e5fc6f9ae68dc5ebd8252047b8e78e3b

With a few releases still planned for Python 2.7 before EOL according to Pep 373, while this is not directly a security issue it does block the use of the latest OpenSSL package and seems like a useful inclusion to the last few releases. Happy to submit a backport PR (in progress) if that's likely.

Reproduce steps here: 

https://github.com/CaseyFaist/reproduceSNIcase
msg349136 - (view) Author: Casey (cfactoid) * Date: 2019-08-06 21:49
Update: After digging further (and enabling the "Less secure app access" setting on the test Google account) it looks like Python 2.7 caps TLS at 1.2 rather than using 1.3 when OpenSSL is upgraded. This prevents breakage, and it looks like the SSLSocket class silences the handshake complaints.

If this were an active branch, this could be worth revisiting - but since 2.7 is soon to be EOL and we can't reproduce the breakage, not sure it's worth it.
History
Date User Action Args
2019-08-06 21:49:23cfactoidsetstatus: open -> closed
type: crash -> behavior
messages: + msg349136

stage: resolved
2019-08-06 19:49:52cfactoidcreate