Bug 1603597 - Confusing error message when asking for invalid DSA parameter sizes in FIPS mode
Summary: Confusing error message when asking for invalid DSA parameter sizes in FIPS mode
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openssl
Version: 7.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Hubert Kario
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-19 17:26 UTC by Hubert Kario
Modified: 2018-10-30 11:25 UTC (History)
2 users (show)

Fixed In Version: openssl-1.0.2k-16.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 11:24:02 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:3221 None None None 2018-10-30 11:25:57 UTC

Description Hubert Kario 2018-07-19 17:26:32 UTC
Description of problem:
When system is working in FIPS mode, only specific key sizes are allowed, asking openssl for generation of other key sizes causes it to report confusing error message "q not prime" instead of the expected "key size invalid"

Version-Release number of selected component (if applicable):
openssl-1.0.2k-15.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. turn system to FIPS mode
2. openssl dsaparam -out dsa-test.pem 2047

Actual results:
Generating DSA parameters, 2047 bit long prime
This could take some time
140075572418448:error:0A07B071:dsa routines:dsa_builtin_paramgen:q not prime:dsa_gen.c:165:
Error, DSA key generation failed

Expected results:
Generating DSA parameters, 2047 bit long prime
This could take some time
140178529699744:error:0A07B071:dsa routines:dsa_builtin_paramgen:key size invalid:dsa_gen.c:167:
Error, DSA key generation failed

Additional info:
while technically a regression (openssl-1.0.1e-60.el7.x86_64 was behaving correctly), it's only an issue in error message

Comment 9 errata-xmlrpc 2018-10-30 11:24:02 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, 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/RHSA-2018:3221


Note You need to log in before you can comment on or make changes to this bug.