Bug 1110750
Summary: | gnutls should use the central certificate store | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Nikos Mavrogiannopoulos <nmavrogi> |
Component: | gnutls | Assignee: | Nikos Mavrogiannopoulos <nmavrogi> |
Status: | CLOSED ERRATA | QA Contact: | Stanislav Zidek <szidek> |
Severity: | unspecified | Docs Contact: | Mirek Jahoda <mjahoda> |
Priority: | high | ||
Version: | 7.1 | CC: | amarecek, bressers, ksrot, lmiksik, pvrabec, stefw, szidek, tmraz |
Target Milestone: | rc | Keywords: | Rebase, Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | gnutls-3.3.22-1.el7 | Doc Type: | Enhancement |
Doc Text: |
_gnutls_ now uses the central certificate store
The _gnutls_ packages provide the GNU Transport Layer Security (GnuTLS) library, which implements cryptographic algorithms and protocols such as SSL, TLS, and DTLS. With this update, GnuTLS uses the central certificate store of Red Hat Enterprise Linux through the _p11-kit_ packages. Certificate Authority (CA) updates, as well as certificate black lists, are now visible to applications at runtime.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 00:58:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1110696, 1122528, 1142305, 1174191 | ||
Bug Blocks: | 1295396, 1296594, 1309228, 1313485 |
Description
Nikos Mavrogiannopoulos
2014-06-18 11:28:21 UTC
With the rebase of both gnutls and p11-kit, this fix is a simple configuration change in gnutls (i.e., compile with the flag --with-default-trust-store-pkcs11="pkcs11:" as in Fedora 21) Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. 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/RHBA-2016-2218.html |