Title: RE: Is there a known issue with the Release version of the FIPS c ompl iant 5.0.4 Crypto++?

Wei,

As I understand it, an enterprise that makes use of your FIPS certified DLL can pursue an "OEM Certification".  This is an abbreviated form of certification that would actually extend to the product that uses the DLL in addition to the DLL itself.  It would be abbreviated because they only examine the manner in which a previously certified libary is used rather than a complete certification of the algorithms as well.

Here is the text from the FIPS documentation:

vvvvvvvvvvvvvvv
After the OEM module is validated, the CMT Lab can submit a non-security letter request asserting that the OEM module is identically the same as the module which the 3rd party wishes to re-brand or re-sell, and the CMT Lab has reviewed the agreement between the 3rd party and the OEM module vendor that both parties agree to this arrangement. The CMVP will then update the web site with the 2nd module information within the limits of the existing database format. No new or additional certificates will be printed. See Certificate #141 as an example.

^^^^^^^^^^^^^^^

My question for you is - Do you allow third-party users of your FIPS compliant DLL to use it to gain an OEM certification for themselves?

Thanks...

-- 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.

Reply via email to