Dave, I am linking libeay32.lib. I did try the .dll and tried to make it a "reference" in a VS2008 project, but that completely failed.
If I understand correctly "ssleay32" is needed to implement SSL/TLS protocols? If so, I definitely need to include it. But, currently my linking issues don't seem to be affected by this library being included or not. My link issues are either : 1) Can't find FIPS symbols (FIPS_hmac_final, FIPS_hmac_init_ex) OR 2) with fipscanister.lib also linked - duplicate symbols int MSVCRT.lib and LIBCMT.lib (like __exit, _raise and _malloc) I think a simple, basic make file for a windows console application would greatly help me track down my linker issues. I'm sure it is some simple mismatch or mistake I make in the make file I sourced from nt.mak. I just can't seem to pinpoint it. Thanks, -Jon -----Original Message----- From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Dave Thompson Sent: Monday, February 04, 2013 1:58 PM To: openssl-users@openssl.org Subject: RE: Compiling openssl fips in Windows >From: owner-openssl-us...@openssl.org On Behalf Of Jon Evers >Sent: Friday, 01 February, 2013 17:45 >I'm trying to link an application that will use openssl and fips. >I'm getting linker errors <snip> [using] MS Visual Studio 2008. >I'm trying to link the DLL, lib32eay.dll. Did you put libeay32.dll in the VS "project" or libeay32.lib ? VS needs the latter. You *link* with the export library and then *run* with the dll (from the same build, or at least a build which is binary compatible) and if the dll is not in your PATH I think you need a setting for that also. To answer your other question elsethread, you similarly need ssleay32 if and only if your app uses protocol functions. libeay on Windows (libcrypto on Unix) provides crypto primitives (like AES_* RC4_* SHA_* etc), some "utility" primitives like ASN1_* PEM_* BIO_* PEM_*, and the "generic wrapper" EVP_*. Parts of libeay/libcrypto (only) are "replaced" in FIPS mode. (Actually the normal versions are still there, but not used.) ssleay (libssl) implements "SSL" protocol (including TLS and DTLS, which technically are slightly different) *using* libeay/libcrypto, and thus using FIPS primitives if enabled. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org 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. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
