Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
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
|
Detailsmitmproxy 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
Monday, 25 April 2022, 20:20 GMT
Reason for closing: Fixed
Additional comments about closing: python-cryptography 36.0.0-1
pip install --user "cryptography<35.0.0"
It works for me.