LM, I was using the Jan 18, 2013 version. It looks like the current is now Jan 25, 2013. However, those sections and paragraphs I quoted are still there. Just look down a few paragraphs to find them.
Section 5.3.2 seems to be the root of my problem. I don't think my project, based on ms\nt.mak, is working correctly. As a makefile example, nt.mak is fairly complex and I had to trace and pull out quite a few symbols and modify them to get it to run. Does anyone have a basic make file for Windows that links the openssl and fips libraries or maybe a simple VS2008 project that they can post or send me? Thanks for any help. -Jon Section 5.3.2 The static library Makefile ms\nt.mak in the OpenSSL distribution gives an example of the usage of fipslink.pl. ________________________________ From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Memmott, Lester Sent: Monday, February 04, 2013 2:51 PM To: openssl-users@openssl.org Subject: RE: Compiling openssl fips in Windows Jon, Regarding: According to my interpretation of the documentation, it should be included in libeay32.dll: Section 2.4.2 Note that except in the most unusual circumstances the FIPS Object Module itself (fipscanister.o) is not linked directly with application code. Section 4.3.3 The resulting FIPS capable OpenSSL can be used for shared or static linking. The shared library built (when ms\ntdll.mak is used as the Makefile) links fipscanister.lib into libeay32.dll using fipslink.pl I wonder if you're working off of an older version of the documentation. I've been using the User Guide v2.0 found here: http://www.openssl.org/docs/fips/UserGuide-2.0.pdf Thanks, LM Live customer support is available 24/7/365 from the U.S. for all customers worldwide and locally in other countries. Find out more at www.go2vanguard.com. Enable Yourself Learn more about Vanguard zSecurity University training classes offered online, on-demand by request, or in a traditional classroom setting in cities worldwide. www.go2vanguard.com This e-mail and any attachments are intended solely for the use of the addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination of this e-mail or any attachments is strictly prohibited. If you have received this e-mail in error, please do not read this email, please delete all copies of this e-mail and any attachments and notify the sender immediately. Thank you.
