The description under the algorithm lists is premature. Crypto++ is not yet FIPS 140-2 validated. There was a big delay because NIST refused to accept Crypto++ in static library form, even though they (verbally) indicated a year ago that they would. So I had to switch over to a DLL. Download will be made available when validation is finalized. I am now hoping for end of August.
On Thu, Jul 24, 2003 at 10:50:46AM -0400, Chris Hofstaedter wrote: > I noticed that version 5.01 is listed with a status of "140-2 validated" for > at least the AES and 3DES (among others) on the Win32 platform: > http://csrc.nist.gov/cryptval/aes/aesval.html > http://csrc.nist.gov/cryptval/des/tripledesval.html > > In each site, they describe that "The pre-compiled Win32 static library is > FIPS 140-2 Level 1 validated.". However, as far as I can tell from the > Crypto++ home page, the FIPS status is that it is still being evaluated for > compliance. Is this because it is only validated in a limited sense (win32 > with certain algorithms)? Either way, do you have any (even rough) guess as > to when it will be made available for download? Thanks in advance... > > -- Chris Hofstaedter > > > The information contained in this e-mail message is intended only for the > personal and confidential use of the recipient(s) named above. If the reader > of this message is not the intended recipient or an agent responsible for > delivering it to the intended recipient, you are hereby notified that you > have received this document in error and that any review, dissemination, > distribution, forwarding, or otherwise copying of this message is strictly > prohibited. If you have received this communication in error, please notify > Padcom immediately by e-mail at [EMAIL PROTECTED] and delete the > original message. Although Padcom utilizes industry accepted methods to > scan email and attachments for viruses, it does not guarantee that either is > virus-free and accepts no liability for any damage sustained as a result of > viruses. Padcom makes no representation or warranty (express or implied) as > to the accuracy or completeness of any information provided in this e-mail > message and expressly disclaims any and all liability that may be based on > information contained therein.
