Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1367484 - Backport upstream "alternate trust paths" fix to glib-networking in RHEL 7
Backport upstream "alternate trust paths" fix to glib-networking in RHEL 7
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glib-networking (Show other bugs)
7.4
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Dan Winship
Desktop QE
:
Depends On:
Blocks: 1335930 rhel7-remove-legacy-cas
  Show dependency treegraph
 
Reported: 2016-08-16 10:14 EDT by Kai Engert (:kaie) (inactive account)
Modified: 2017-08-01 08:28 EDT (History)
7 users (show)

See Also:
Fixed In Version: glib-networking-2.50.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 08:28:09 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2100 normal SHIPPED_LIVE GTK+ bug fix update 2017-08-01 12:06:50 EDT

  None (edit)
Description Kai Engert (:kaie) (inactive account) 2016-08-16 10:14:57 EDT
We'd like to fix bug 1367434 in RHEL 7.4 to avoid having to trust legacy CAs that have already been removed by the upstream Mozilla CA list maintainers.

In order to avoid regressions in applications that use glib-networking, a code enhancement is required, which has been implemented by upstream already.

Dan offered to help with the development work, which will require either a rebase to glib-networking 2.48, or to backport the relevant changes.

See also:
https://bugzilla.gnome.org/show_bug.cgi?id=750457
https://bugzilla.gnome.org/show_bug.cgi?id=753260
and bug 1284655 and bug 1246492
Comment 14 errata-xmlrpc 2017-08-01 08:28:09 EDT
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://access.redhat.com/errata/RHBA-2017:2100

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