FS#72408 - [mitmproxy] Broken by python-cryptography >= 35

Attached to Project: Community Packages
Opened by Ronan Pigott (Brocellous) - Wednesday, 13 October 2021, 02:15 GMT
Last edited by David Thurstenson (thurstylark) - Monday, 25 April 2022, 20:20 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
kpcyrd (kpcyrd)
Filipe Laíns (FFY00)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

mitmproxy produces an error on startup with a python traceback. The error w/o traceback is as follows:

ValueError: Valid PEM but no BEGIN CERTIFICATE/END CERTIFICATE delimiters. Are you sure this is a certificate?

The cause is a breaking change in python-cryptography 35.0.0 [1]. The bug is tracked upstream by [2], and it looks like it has been fixed as well by [3], but not yet released.

[1] https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst#id8
[2] https://github.com/pyca/cryptography/issues/6351
[3] https://github.com/pyca/cryptography/pull/6365
This task depends upon

Closed by  David Thurstenson (thurstylark)
Monday, 25 April 2022, 20:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  python-cryptography 36.0.0-1
Comment by Tateuchi Ayaka (ssr) - Thursday, 14 October 2021, 01:41 GMT
Temporary fix:

pip install --user "cryptography<35.0.0"

It works for me.
Comment by Fijxu (FIjxu) - Sunday, 17 October 2021, 04:28 GMT
The temporary fix works for now but the issue is still alive at this time
Comment by kpcyrd (kpcyrd) - Friday, 19 November 2021, 13:15 GMT
https://github.com/mitmproxy/mitmproxy/issues/4917
Comment by Ronan Pigott (Brocellous) - Saturday, 18 December 2021, 22:16 GMT
I think this has been resolved by the release of python-cryptography 36.0.0

Loading...