RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1315758 - Update to the most recent version of PEP493
Summary: Update to the most recent version of PEP493
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Charalampos Stratakis
QA Contact: Branislav Náter
Lenka Špačková
URL:
Whiteboard:
Depends On:
Blocks: 1305230
TreeView+ depends on / blocked
 
Reported: 2016-03-08 14:21 UTC by Robert Kuska
Modified: 2016-11-03 20:16 UTC (History)
8 users (show)

Fixed In Version: python-2.7.5-41.el7
Doc Type: Release Note
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2016-11-03 20:16:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2586 0 normal SHIPPED_LIVE Low: python security, bug fix, and enhancement update 2016-11-03 12:09:15 UTC

Comment 11 Nick Coghlan 2016-08-26 01:29:04 UTC
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"

Comment 12 Tomas Hoger 2016-08-26 08:18:43 UTC
(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:

https://access.redhat.com/articles/2039753#controlling-and-troubleshooting-certificate-verification-6

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.

Comment 13 Nick Coghlan 2016-09-22 07:48:38 UTC
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.

Comment 15 errata-xmlrpc 2016-11-03 20:16:45 UTC
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.

https://rhn.redhat.com/errata/RHSA-2016-2586.html


Note You need to log in before you can comment on or make changes to this bug.