298513 - Implement pairwise consistency test for key transport key generation FIPS 140-2

Status: RESOLVED FIXED

(NSS :: Libraries, defect, P1)

Description

[glen beasley]

Implement pairwise consistency test after the generation of keys for key transport
when ever we generate a new key pair. (Conditional self test.)

VE 09.31.01

Comment 1

[glen beasley]

we are already doing this in pk11wrap, we need to move it into the softoken
under the PKCS#11 boundary. 

Comment 2

[Nelson Bolyard (seldom reads bugmail)]

How is this bug different from bug 298514?
What needs to be done for this bug that does not also 
need to be done for bug 298514, and vice versa?
Are different functions involved? or ??

Comment 3

[Wan-Teh Chang]

Nelson: bug 298514 is for public/private keypairs used for
*digital signature*.  This bug is for keypairs used for key
transport.

Although the patch in bug 298514 addresses this bug, I can't
mark this bug fixed until I've confirmed that all the FIPS
key transport methods have been covered.  (I've confirmed
that all the FIPS digital signature methods have been covered,
which is why bug 298514 was marked fixed.)

Comment 4

[Wan-Teh Chang]

This bug has been fixed by the patch in bug 298514.

RSA encryption is the only FIPS approved key transport
method that VE.09.31.01 applies to.  The other key
transport/establishment methods either use a symmetric
wrapping key (encrypting/wrapping with TDES or AES) or
require two public/private key pairs (Diffie-Hellman or
its elliptic curve variants).