Bug 1685325

Summary: PQG verify fails when create DSA PQG parameters because the counts aren't returned correctly.
Product: Red Hat Enterprise Linux 8 Reporter: Bob Relyea <rrelyea>
Component: nssAssignee: Bob Relyea <rrelyea>
Status: CLOSED ERRATA QA Contact: Simo Sorce <ssorce>
Severity: unspecified Docs Contact:
Priority: high    
Version: 8.1CC: cww, dueno, hkario, mthacker, nmavrogi, rcadova, snagar, ssorce, toneata
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-30 19:49:59 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: 1677443, 1701002    
Attachments:
Description Flags
Fix PQG to 1) update counter values, 2) handle verify with new counters, 3) create seeds correctly if seedlen > 512 none

Description Bob Relyea 2019-03-05 00:40:10 UTC 
PQG verification fails because the counts are returned correctly. This can cause PGG generation to fail unless the parameters are very specifically crafted.
Comment 5 Bob Relyea 2019-04-23 18:10:38 UTC 
Created attachment 1557837 [details]
Fix PQG to 1) update counter values, 2) handle verify with new counters, 3) create seeds correctly if seedlen > 512
Comment 6 Bob Relyea 2019-05-09 22:08:04 UTC 
NOTE: this patch is being reviewed upstream, It's not yet pushed there yet.
Comment 11 Simo Sorce 2019-06-21 15:45:25 UTC 
Patch is in SRPM and was applied at build time.
Comment 16 errata-xmlrpc 2019-07-30 19:49:59 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-2019:1951