Closed Bug 167605 Opened 22 years ago Closed 22 years ago

RFE: Implement SHA-256, SHA-384, SHA-512 and related algorithms

Categories

(NSS :: Libraries, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: thayes0993, Assigned: nelson)

References

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
Build Identifier: 

FIPS 180-2 has been publised by NIST and will be effective in February 2003. It 
defines three new SHA-like secure hash functions that have longer output 
blocks. In particular, SHA-256 has a 256 bit output, which matches the security 
of 128-bit encryption algorithms.

The three algorithms and provisional OIDs are:

    SHA-256:    2.16.840.1.101.3.4.2.1
    SHA-384:    2.16.840.1.101.3.4.2.2
    SHA-512:    2.16.840.1.101.3.4.2.3

In addition, a signature algorithm based on SHA-256 with RSA encryption should 
be implemented.  The OID for this is not yet known.

These four algorithms (three SHA and one new signature algorithm) will need to 
have PKCS #11 mechanism types assigned for them as well.


Reproducible: Always

Steps to Reproduce:
Status: UNCONFIRMED → NEW
Ever confirmed: true
The OIDs for RSA signatures using the new hash algorithms are:

sha256WithRSAEncryption    OBJECT IDENTIFIER ::= { pkcs-1 11 }
sha384WithRSAEncryption    OBJECT IDENTIFIER ::= { pkcs-1 12 }
sha512WithRSAEncryption    OBJECT IDENTIFIER ::= { pkcs-1 13 }

These are from the new PKCS-1 v2.1 (published June 14, 2002)
nelsonb@netscape.com is interested in implementing the new SHS algorithms.  
Adding him to the CC list.
*** Bug 86106 has been marked as a duplicate of this bug. ***
Assigned the bug to Nelson.  Tentatively target NSS 3.7.
Assignee: wtc → nelsonb
Priority: -- → P1
Whiteboard: [3.7]
Whiteboard: [3.7]
Target Milestone: --- → 3.7
Blocks: 181540
Moved to target milestone 3.8 because the original
NSS 3.7 release has been renamed 3.8.
Target Milestone: 3.7 → 3.8
This work was checked in some time ago.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.