python3.4.3 SRU break requests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-urllib3 (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Matthias Klose | ||
python-virtualenv (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Matthias Klose |
Bug Description
SRU reproducer / acceptance criteria: see comment #6
Sicne the upgade to python 3.4.3 on trusty, I'm getting this error when using a squid proxy:
https:/
The code is using python-requests, with verify=True for ssl connection (default). Some tests are testing that invalid certificates are rejected: https:/
Rerunning the same code with previous trusty package (3.4.0~trusty1) doesn't show up this issue. It seems that SNI is broken for the trusty version of python3-requests with 3.4.3. (See the FAQ http://
I did run a test, grabbing requests 2.7 and backporting it to trusty (I needed to as well to take python3-urllib3 willy version).
So, 3.4.3 has an incompatible change for existing projects and people with proxys are starting to see some breakage like in https:/
Can we get it fix somehow, reverting the incompatible change breaking SNI (I wonder if this is "Changed in version 3.4.3: This class now performs all the necessary certificate and hostname checks by default. To revert to the previous, unverified, behavior ssl._create_
Related branches
tags: | added: trusty |
Changed in python3.4 (Ubuntu Trusty): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in python3.4 (Ubuntu): | |
status: | Confirmed → Triaged |
tags: | added: regression-update |
Changed in python3.4 (Ubuntu): | |
assignee: | Barry Warsaw (barry) → nobody |
Changed in python3.4 (Ubuntu Trusty): | |
assignee: | nobody → Matthias Klose (doko) |
Changed in python3.4 (Ubuntu): | |
status: | Triaged → Invalid |
affects: | python3.4 (Ubuntu) → python-urllib3 (Ubuntu) |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.