Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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.
DescriptionWilliam Yardley
2015-02-26 18:27:10 UTC
Description of problem:
When connecting to a new system via TLS / SSL, Mutt requires the user to save the certificate.
Version-Release number of selected component (if applicable):
1.5.20-7.20091214hg736b6a.el6
How reproducible:
Very
Steps to Reproduce:
1. Configure spoolfile (or folder, etc.) as imaps://[some host with valid cert]
Actual results:
Mutt prompts the user to save the certificate
Expected results:
Mutt uses the system default CA bundle in /etc/pki/tls/certs/ca-bundle.crt from the ca-certificates RPM.
Additional info:
Compiled in default is unset:
In muttrc(5):
ssl_ca_certificates_file
Type: path
Default: “”
It also appears to not be configured in default configuration:
smtp01:$ rpm --verify mutt
smtp01:$ grep ssl_ca_certificates /etc/Muttrc | grep -v ^#
smtp01:$
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
Description of problem: When connecting to a new system via TLS / SSL, Mutt requires the user to save the certificate. Version-Release number of selected component (if applicable): 1.5.20-7.20091214hg736b6a.el6 How reproducible: Very Steps to Reproduce: 1. Configure spoolfile (or folder, etc.) as imaps://[some host with valid cert] Actual results: Mutt prompts the user to save the certificate Expected results: Mutt uses the system default CA bundle in /etc/pki/tls/certs/ca-bundle.crt from the ca-certificates RPM. Additional info: Compiled in default is unset: In muttrc(5): ssl_ca_certificates_file Type: path Default: “” It also appears to not be configured in default configuration: smtp01:$ rpm --verify mutt smtp01:$ grep ssl_ca_certificates /etc/Muttrc | grep -v ^# smtp01:$