>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
