Re: [openssl-users] OpenSSL FOM 2.0.12 - Windows Compliance

/2016 07:20 AM, Imran Ali wrote: > Hi Guys, > > > > I need some help. I am looking for some evidence which I can provide > to my auditor for FOM 2.0.12 is FIPS-140 compliance when compiled and > used in Windows environment. When I look at the NIST web site under > htt

[openssl-users] OpenSSL FOM 2.0.12 - Windows Compliance

cannot see 2.0.12 version. Is there something I am missing? Regards, Imran Ali Engineering Product Lead [cid:image001.gif@01CE15D3.C9808950] t: +44 (0) 118 943 0485 m: +44 (0) 780 113 7865 w: www.enghouseinteractive.com<http://www.enghouseinteractive.com/> e: imran@enghou

Re: [openssl-users] FIPS Certification

On 27/01/2016 16:24, Imran Ali wrote: > > All, > > Looking at the website > http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm > > There is a new date of 01/25/2016 under Validation against OpenSSL > Software Foundation <http://openssl.com/> (2473).

[openssl-users] FIPS Certification

All, Looking at the website http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm There is a new date of 01/25/2016 under Validation against OpenSSL Software Foundation (2473). Does that mean that we now have a FIPS compliant Open SSL again? Regards, Imran

Re: [openssl-users] FIPS Certification

/ms724832(v=vs.85).aspx Regards, Imran -Original Message- From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of Steve Marquess Sent: 27 January 2016 16:55 To: openssl-users@openssl.org Subject: Re: [openssl-users] FIPS Certification On 01/27/2016 11:34 AM, Imran Ali wrote

[openssl-users] OpenSSL FIPS Object Module v2.0

Hi Steve, Is there any update on the submissions for the OpenSSL FIPS Object Module v2.0, validation(s) #1747/#2398/#2474 Regards, Imran ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] FIPS 140-2 X9.31 RNG transition expenses

Thanks Steve, I was more concerned on the news that openssl may not be FIPS compliant because of: 'sunsetting' older FIPS validations and the reasoning behind the change has to do with the Random Number Generators (RNG). As of December 31, 2015, ANSI X9.31 and X9.62 RNG's will no longer be

Re: [openssl-users] FIPS 140-2 X9.31 RNG transition expenses

Hi Steve, Just want to confirm on this item. Are we saying that to get openssl back to be FIPS compliance is just a paper shuffle. If so is there any expected eta on it as our team is using openssl version for a security project and we need a fips compliance library. Regards, Imran