Please convert to use the system's crypto policy for SSL and TLS:
If this program is compiled against gnutls, change the default priority string to be "@SYSTEM" or to use gnutls_set_default_priority().
If this program is compiled against openssl, and there is no default cipher list specified, you don't need to modify it. Otherwise replace the default cipher list with "PROFILE=SYSTEM".
In both cases please verify that the application uses the system's crypto policies.
If the package is already using the system-wide crypto policies, or it does not use SSL or TLS, no action is required, the bug can simply be closed.
I see there are some calls to SSL_CTX_set_cipher_list() at Modules/_ssl.c
Christian would you be able to shed some light here?
SSL_CTX_set_cipher_list() is called in two places. First of all it is used in the constructor of SSLContext to block unsafe ciphers with old versions of OpenSSL. It is also called by SSLContext.set_ciphers() in ssl.create_default_context(). You have to patch both calls to use system policies.
In order to avoid using a downstream-only string (PROFILE=SYSTEM), you may want to not call these functions at all, unless the caller has explicitly specified a string. Not calling the set_ciphers() in openssl, means using the default ciphers.
I opened upstream bug https://bugs.python.org/issue31429 to address the issue. While Python won't drop the cipher suite override any time soon, I'll try to get a configure option and macro in:
Thanks Christian for looking into it.
Nikos for which branches of Fedora should this be addressed and is there any related deadline? Currently I'm still catching up with things due to a long vacation, so it might take some time until I get to it.
Current WIP PR from cheimes:
I backported the PR to python 3.6.2 and created a scratch build and it builds fine on rawhide with using the "PROFILE=SYSTEM" string.
Upstream has merged the PR for the 3.7 branch. I will backport it to our 3.6 package as it's backwards compatible.
python3-3.6.4-7.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-0910fcb732
python3-3.6.4-7.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-0910fcb732
python3-3.6.4-7.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
python3-debug.x86_64: W: crypto-policy-non-compliance-openssl /usr/lib64/python3.6/lib-dynload/_ssl.cpython-36dm-x86_64-linux-gnu.so SSL_CTX_set_cipher_list
python3-libs.x86_64: W: crypto-policy-non-compliance-openssl /usr/lib64/python3.6/lib-dynload/_ssl.cpython-36m-x86_64-linux-gnu.so SSL_CTX_set_cipher_list
Looking at https://src.fedoraproject.org/rpms/python3/c/c9bb114a1dc3fc2216af482d1cdbafe58db45afb?branch=master
I don't see --with-ssl-default-suite="PROFILE=SYSTEM"
Ignore the last comment.
The fix is actually https://src.fedoraproject.org/rpms/python3/c/969d51434e2479639d62c2b03fd51df7403eb722?branch=master
That has --with-ssl-default-suites=openssl, not --with-ssl-default-suite="PROFILE=SYSTEM".
Apparently, rpmlint does something like this:
$ readelf -W -S -l -d -s /usr/lib64/python3.6/lib-dynload/_ssl.cpython-36m-x86_64-linux-gnu.so | grep SSL_CTX_set_cipher_list | grep -v 'PROFILE=SYSTEM'
17: 0000000000000000 0 FUNC GLOBAL DEFAULT UND SSL_CTX_set_cipher_list@OPENSSL_1_1_0 (2)
Reassigning to rpmlint as this is not a bug in python but an erroneous reporting of rpmlint.
rpmlint matches https://fedoraproject.org/wiki/Packaging:CryptoPolicies
If that is incorrect, it should be adjusted (and rpmlint will match it).
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 29 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.