ol'fogey wrote: > ... >>From http://csrc.nist.gov/CryptoToolkit/tkdigsigs.html there are only > 3 approved functions to generate a digital signature. The caveat > appears to be that the method chosen must use an approved hash code > function, as listed on http://csrc.nist.gov/CryptoToolkit/tkhash.html > When I cross reference the approved hash code functions with the hash > code functions used by Cryptopp, there is no match. So does this mean > that the digital signatures in Cryptopp are no not FIPS approved? If > so, could I make the signature myself by creating a hash code of the > file via an approved method like SHA-256 and then using RSA to encrypt > that hash code to create a signature? Can somebody shed some light on > this for me or point me in the right direction with some links?
Crypto++ does indeed support the [approved] SHA-2 family of hashes, as shown on the first pages of both the site and reference manual... so what was the question? :) Robert Roessler [EMAIL PROTECTED] http://www.rftp.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [EMAIL PROTECTED] More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
