Bug 1883976

Summary: mutt on fedora 33 beta fails to connect to mail server with gnutls_handshake failure.
Product: [Fedora] Fedora Reporter: Harish Pillay <hpillay>
Component: muttAssignee: Matej Mužila <mmuzila>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 33CC: abokovoy, athoscribeiro, dakingun, hhorak, jjelen, jmmahler, jpacner, jpazdziora, me, mmuzila, ptalbert, vondruch
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-30 16:35:03 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:

Description Harish Pillay 2020-09-30 16:21:54 UTC
Description of problem:
mutt (version 1.14.6) on a Fedora 33 beta system fails to connect to the mail server with the error: 

"gnutls_handshake: The Diffie-Hellman prime sent by the server is not acceptable" 

Version-Release number of selected component (if applicable):
mutt 1.14.6, Fedora 33 beta

How reproducible:
With Fedora 33 beta installed, and a properly setup mutt, the connect to the server fails with the gnutls_handshake error

Actual results:
gnutls_handshake: The Diffie-Hellman prime sent by the server is not acceptable 

Expected results:
to be able to read/send email.

Additional info:
Filed a helpdesk request and IT came back suggesting the following:
https://fedoraproject.org/wiki/Changes/StrongCryptoSettings to 'update-crypto-policies --set LEGACY'

Comment 1 Harish Pillay 2020-09-30 16:25:20 UTC
by following the recommendation from Red Hat IT to set the crypto policies to legacy, mutt is able to connect successfully.

Comment 4 Patrick Talbert 2020-11-06 12:49:43 UTC
Another safer alternative to using LEGACY is to use the FEDORA32 module:

$ grep ^# /usr/share/crypto-policies/policies/modules/FEDORA32.pmod
# If this policy module is applied to the DEFAULT policy it provides
# the same policy as in the Fedora 32 DEFAULT policy
# DH params size: >= 1023
# SHA1 enabled in signatures
# TLS protocols: TLS >= 1.0 DTLS >= 1.0


So then:

# update-crypto-policies --set DEFAULT:FEDORA32

Comment 5 Ben Cotton 2021-11-04 17:22:05 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2021-11-30 16:35:03 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.