<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><tt>The unfortunate people who are
legally required to use <br>
FIPS-validated crypto are legally restricted to use <br>
*only* the crypto sw/hw on the FIPS validated list and <br>
*only* in the specific configurations (OS etc.) listed <br>
for each on that list.</tt><tt><br>
<br>
Everybody else is better off not trying to use FIPS-<br>
restricted modes and setups.<br>
<br>
</tt><tt>Those who make software for use by the unfortunate <br>
people obviously have to stay within the limits of <br>
what they are allowed to use, but only in software <br>
for them.</tt><br>
<br>
On 27/01/2016 17:34, Imran Ali wrote:<br>
</div>
<blockquote class=" cite"
id="mid_760295c23ed44fd594f27d5e2aec59a8_UK_MAIL_001_edge_local"
cite="mid:760295c23ed44fd594f27d5e2aec59a8@UK-MAIL-001.edge.local"
type="cite">
<pre wrap="">I might be asking asking a very basic question so do apologies upfront but I need to have a clear understanding on this.
The platforms mentioned under #1747 and #2473 does not contain the latest versions of Operating System e.g. Windows 2012 R2 and Windows 10. Does this have any impact on the certification or these libraries can now be used on any OS.
Regards,
Imran
-----Original Message-----
From: openssl-users [<a class="moz-txt-link-freetext" href="mailto:openssl-users-bounces@openssl.org">mailto:openssl-users-bounces@openssl.org</a>] On Behalf Of Jakob Bohm
Sent: 27 January 2016 15:54
To: <a class="moz-txt-link-abbreviated" href="mailto:openssl-users@openssl.org">openssl-users@openssl.org</a>
Subject: Re: [openssl-users] FIPS Certification
On 27/01/2016 16:24, Imran Ali wrote:
</pre>
<blockquote class=" cite" id="Cite_2045799" type="cite">
<pre wrap="">All,
Looking at the website
<a class="moz-txt-link-freetext" href="http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm">http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm</a>
There is a new date of 01/25/2016 under Validation against OpenSSL
Software Foundation <a class="moz-txt-link-rfc2396E" href="http://openssl.com/"><http://openssl.com/></a> (2473). Does that mean that
we now have a FIPS compliant Open SSL again?**
**
</pre>
</blockquote>
<pre wrap="">According to yesterday's post by Steve Marquess, the platforms listed under validation #1747 and
#2473 are OK (for now), but the platforms listed under validation #2398 are still at risk unless
#2398 too gets updated before January 31.
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. <a class="moz-txt-link-freetext" href="https://www.wisemo.com">https://www.wisemo.com</a>
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded </pre>
</body>
</html>