3 <!--#include virtual="/inc/head.shtml" -->
5 <!--#include virtual="/inc/banner.shtml" -->
8 <div class="blog-index">
10 <header><h2>FIPS-140</h2></header>
11 <div class="entry-content">
13 <p>The current validation of a cryptographic
14 module (Module) compatible with the OpenSSL 1.0.2
15 is v2.0.16, FIPS 140-2 certificate <a
16 href="https://csrc.nist.gov/projects/cryptographic-module-validation-program/Certificate/1747">#1747</a>.
17 This Module is documented in the
18 <a href="fips/UserGuide-2.0.pdf">2.0 User Guide</a>;
19 the <a href="/source/openssl-fips-2.0.16.tar.gz">source code</a>,
20 and <a href="fips/SecurityPolicy-2.0.16.pdf">Security Policy</a>
24 For various bureaucratic reasons, the same module is also
25 available as validation <a
26 href="https://csrc.nist.gov/projects/cryptographic-module-validation-program/Certificate/2398">#2398</a>
31 Neither validation will work with any release other than 1.0.2.
32 The OpenSSL project is no longer maintaining either the 1747
33 or the 2398 module. This includes adding platforms to those
35 We are starting work on a new validation, after the 1.1.1
37 That module will have a small set of validated operational
39 The OpenSSL project is no longer involved in private label
40 validations nor adding platforms to the existing certificates.
44 Here is the complete set of files. Note that if you are interested
45 in the "1747" validation, you only need the three files mentioned
51 <td>Date </td>
54 <!--#include virtual="fips.inc" -->
58 <h3><a name="background">Background</a></h3>
60 <p>Please please read the <a
61 href="fips/UserGuide.pdf">User Guide</a>.</p>
65 <li>OpenSSL itself is not validated. Instead a special
66 carefully defined software component called the OpenSSL FIPS
67 Object Module has been created. This Module was designed for
68 compatibility with OpenSSL so that products using the OpenSSL
69 API can be converted to use validated cryptography with minimal
72 <li>The OpenSSL FIPS Object Module validation is "delivered" in
73 source code form, meaning that if you can use it exactly as is
74 and can build it (according to the very specific documented
75 instructions) for your platform, then you can use it as
76 validated cryptography on a "vendor affirmed" basis.</li>
78 <li>If even a single line of the source code or build process
80 for your intended application, you cannot use the open
81 source based validated module directly. You must obtain your
88 You are here: <a href="/">Home</a>
89 : <a href=".">Docs</a>
90 : <a href="">FIPS-140</a>
91 <br/><a href="/sitemap.txt">Sitemap</a>
95 <!--#include virtual="sidebar.shtml" -->
98 <!--#include virtual="/inc/footer.shtml" -->