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.

Bug 1086365

Summary: dovecot: mkcert.sh script generates 1024-bit keys and fails in FIPS mode
Product: Red Hat Enterprise Linux 7 Reporter: Alicja Kario <hkario>
Component: dovecotAssignee: Michal Hlavinka <mhlavink>
Status: CLOSED ERRATA QA Contact: David Jež <djez>
Severity: low Docs Contact:
Priority: low    
Version: 7.0CC: dapospis, djez, mhlavink, nmavrogi, omoris, ovasik
Target Milestone: rcKeywords: Security
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dovecot-2.2.36-7.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1411163 1631796 (view as bug list) Environment:
Last Closed: 2020-09-29 19:54:52 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: 1411163, 1465906, 1570035, 1631796, 1780582    

Description Alicja Kario 2014-04-10 17:19:04 UTC
Description of problem:
mkcert.sh script fails to generate certificate when system is running in FIPS mode

Version-Release number of selected component (if applicable):
dovecot-2.2.10-4.el7.x86_64
openssl-1.0.1e-34.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. Switch system to FIPS mode
2. run /usr/libexec/dovecot/mkcert.sh
3.

Actual results:
Generating a 1024 bit RSA private key
Error Generating Key
139692622727072:error:2D07406D:FIPS routines:RSA_BUILTIN_KEYGEN:invalid key length:rsa_gen.c:190:

Expected results:
Self signed 

Additional info:
Issue caused by default setting in /etc/pki/dovecot/dovecot-openssl.cnf:
[ req ]
default_bits = 1024

New FIPS requirements don't allow RSA key lengths other than 2048 and 3072.

Comment 4 Nikos Mavrogiannopoulos 2018-05-09 13:47:01 UTC
This is not necessarily a FIPS related issue; generating 1024-bit keys by default seems to be a security issue.

Comment 5 Adam Mariš 2018-05-15 10:44:31 UTC
(In reply to Nikos Mavrogiannopoulos from comment #4)
> This is not necessarily a FIPS related issue; generating 1024-bit keys by
> default seems to be a security issue.

I'd rather call this a security hardening, so no CVE, but it surely is recommended to fix this.

Comment 13 errata-xmlrpc 2020-09-29 19:54:52 UTC
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 (dovecot bug fix and enhancement update), 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-2020:3921