New configuration options for SSL/TLS certificate verification for the HTTP clients in the Python standard library
New per-application and per-process configuration options for SSL/TLS certificate verification have been added for the HTTP clients in the Python standard library. The options are described in the 493 Python Enhancement Proposal (https://www.python.org/dev/peps/pep-0493/). The
default global setting continues to be to not verify certificates. For details, see https://access.redhat.com/articles/2039753.
Thanks for getting this into RHEL 7.3!
Checking the RHEL 7.3 beta release notes, this update doesn't currently appear to be mentioned: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html-single/7.3_Release_Notes/index.html
The KB article at https://access.redhat.com/articles/2039753 will also require updates to note that the system-wide default for certification verification can now be flipped to "enable", and then selectively turned off for cases that actually need that by setting "PYTHONHTTPSVERIFY=0"
(In reply to Nick Coghlan from comment #11)
> The KB article at https://access.redhat.com/articles/2039753 will also
> require updates
I can update that kbase. Feel free to reach to me closer to 7.3 GA to do required changes.
> to note that the system-wide default for certification verification can now
> be flipped to "enable",
That's already possible in current version, and should be covered by this section of the article:
Is there anything important missing?
> and then selectively turned off for cases that actually need that by
> setting "PYTHONHTTPSVERIFY=0"
That can/should be added, yes.
Regarding the "system-wide enablement" aspect in the KB, one of the previous arguments against folks doing that by default in their system config was that if an application they or their users needed didn't work in that environment, they were kinda stuck if they couldn't modify the app itself.
With RHEL 7.3+, admins can still change the default even if they or their users have such problematic apps to deal with, since the apps that genuinely can't handle proper verification can be configured to run without it just through an environment modification.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.