NSS incorrectly accepting 1536 bit DH primes in FIPS mode
Categories
(NSS :: Libraries, defect, P1)
Tracking
(Not tracked)
People
(Reporter: rrelyea, Assigned: rrelyea)
References
Details
Attachments
(2 files)
|
4.18 KB,
patch
|
Details | Diff | Splinter Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
When NSS is in FIPS mode, it should reject all primes smaller than 2048. The ike 1536 prime is in the accepted primes table. In FIPS mode it should be rejected.
The attach patch rejects that prime only in FIPS mode. The test cases were update to verify this. I'll submit this patch as a phabricator patch as well.
| Assignee | ||
Updated•4 years ago
|
Comment 1•4 years ago
|
||
Would there be problematic consequences in rejecting even in non-fips mode?
| Assignee | ||
Comment 2•4 years ago
|
||
When NSS is in FIPS mode, it should reject all primes smaller than 2048. The ike 1536 prime is in the accepted primes table. In FIPS mode it should be rejected.
| Assignee | ||
Comment 3•4 years ago
|
||
Probably not in ssl because I think we already reject them in SSL, but old IKE servers wouldn't connect. In general we only do this check if we are 1) in FIPS mode, or 2) the application triggers it by setting CKA_SUBPRIME on the imported key we are checking.
bob
| Assignee | ||
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Updated•4 years ago
|
Description
•