Bug 1196787
Summary: | System default CA bundle not set as default in compiled-in default or config | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | William Yardley <wby+redhat> | ||||
Component: | mutt | Assignee: | Matej Mužila <mmuzila> | ||||
Status: | CLOSED ERRATA | QA Contact: | Lukáš Zachar <lzachar> | ||||
Severity: | unspecified | Docs Contact: | Filip Hanzelka <fhanzelk> | ||||
Priority: | unspecified | ||||||
Version: | 6.8 | CC: | bnater, hhorak, mmuzila | ||||
Target Milestone: | rc | Keywords: | Patch | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
The system default CA bundle has been set as default in the compiled-in default setting or configuration in *mutt*
Previously, when connecting to a new system via TLS/SSL, the *mutt* email client required the user to save the certificate. With this update, the system Certificate Authority (CA) bundle is set in *mutt* by default. As a result, *mutt* now connects via SSL/TLS to hosts with a valid certificate without prompting the user to approve or reject the certificate.
|
Story Points: | --- | ||||
Clone Of: | |||||||
: | 1388511 (view as bug list) | Environment: | |||||
Last Closed: | 2017-03-21 11:18:17 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: | |||||||
Bug Blocks: | 1359256, 1388511 | ||||||
Attachments: |
|
Description
William Yardley
2015-02-26 18:27:10 UTC
Created attachment 1055671 [details]
add path to system ca-bundle to default configuration
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-2017-0732.html |