correction to previous comment. FIPS was built with 'no-asm' too. _Sunil
> On Mar 15, 2014, at 7:24 PM, Sunil <shru...@gmail.com> wrote: > > I hope you are using s_server/s_client with OPENSSL_FIPS=1. > > Below are the steps I used in building OpenSSL with FIPS, please let me know > if anything is unusual here: > > FIPS: > > ms\do_fips.bat > > OpenSSL-FIPS: > > perl Configure VC-WIN32 no-asm no-rc5 no-idea no-ec2m fips > --with-fipslibdir=<fips_install_path> --prefix=c:\somedir\openssl\dir > ms\do_ms.bat > nmake -f ms\ntdll.mak > > Thanks, > Sunil > > > >> On Sat, Mar 15, 2014 at 5:21 PM, Dr. Stephen Henson [via OpenSSL] <[hidden >> email]> wrote: >> On Sat, Mar 15, 2014, Sunil wrote: >> >> > I had some issues when compiling without the "no-asm" option; this can >> > probably be fixed with configuring the right paths. I haven't dug into >> > getting the performance gain since I was focused on resolving the bad >> > record mac error. If it seems related to the issue, then I can work on >> > getting it compiled without the "no-asm" option. >> > >> > Here is the output from cl: >> > >> > Microsoft (R) C/C++ Optimizing Compiler Version 17.00.51106.1 for x86 >> > >> That's odd. I have exactly the same version and don't have any problems with >> s_server/s_client even with no-asm. The only possible difference is I'm >> using >> the latest 1.0.1 snapshot but that shouldn't matter. >> >> Steve. >> -- >> Dr Stephen N. Henson. OpenSSL project core developer. >> Commercial tech support now available see: http://www.openssl.org >> ______________________________________________________________________ >> OpenSSL Project http://www.openssl.org >> Development Mailing List [hidden email] >> Automated List Manager [hidden email] >> >> >> If you reply to this email, your message will be added to the discussion >> below: >> http://openssl.6102.n7.nabble.com/FIPS-capable-OpenSSL-on-windows-failing-with-bad-record-mac-failure-in-a-TLSv1-2-handshake-tp48853p48857.html >> To unsubscribe from FIPS capable OpenSSL on windows failing with bad record >> mac failure in a TLSv1.2 handshake, click here. >> NAML > > > View this message in context: Re: FIPS capable OpenSSL on windows failing > with bad record mac failure in a TLSv1.2 handshake > Sent from the OpenSSL - Dev mailing list archive at Nabble.com.