<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">The fipsinstall program runs the platform tests. I.e. you need to run fipsinstall on the device at some point.<div class=""><br class=""></div><div class=""><br class=""></div><div class="">> Or are you suggesting that the presence of a standalone tool might influence the contents of such a security policy?</div><div class=""><br class=""></div><div class="">Yes. Well maybe. I’ll posit the possibility at the next planning meeting.</div><div class=""><br class=""></div><div class=""><br class=""><div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div>Pauli<br class="">-- <br class="">Dr Paul Dale | Distinguished Architect | Cryptographic Foundations <br class="">Phone +61 7 3031 7217<br class="">Oracle Australia</div><div><br class=""></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 28 Jul 2020, at 9:51 am, Thomas Dwyer III <<a href="mailto:tomiii@tomiii.com" class="">tomiii@tomiii.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">On Mon, Jul 27, 2020 at 3:39 PM Dr Paul Dale <<a href="mailto:paul.dale@oracle.com" class="">paul.dale@oracle.com</a>> wrote:<br class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class="">These are questions better asked of a FIPS lab since they are the experts and we are not.<div class=""><br class=""></div></div></blockquote><div class=""><br class=""></div><div class=""><br class=""></div><div class="">That is a fair response.</div><div class=""><br class=""></div><div class=""> <br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class=""><div class=""></div><div class="">I expect that your alternative installation process’s validity will depend on the security policy and what it says needs to be done. This hasn’t been written yet so there is no answer at this point.</div><div class=""><br class=""></div><div class="">Skipping the self tests is definitely not permitted. The full suite of self tests *must* be run before the module can be used.</div><div class=""><br class=""></div></div></blockquote><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Oops, I didn't mean to suggest skipping the self-tests. I was talking about the callback that fipsinstall currently uses to display results and/or inject faults in the self-tests. I don't think I need that. As long as OSSL_PROVIDER_load() succeeds it seems safe (?) to assume that all the self-tests passed at some point.<br class=""></div><div class=""><br class=""></div><div class=""> <br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class=""><div class=""></div><div class=""><br class=""></div><div class="">You question prompts the possibility of making fipsinstall a standalone executable, this is something we could look into if we get time. I expect we’d look favourably on a pull request that allowed either or both options.</div><div class=""><br class=""></div></div></blockquote><div class=""><br class=""></div><div class=""><br class=""></div><div class="">This is encouraging. However, since there is no draft security policy written yet would this be premature? Or are you suggesting that the presence of a standalone tool might influence the contents of such a security policy?<br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Tom.III</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""> <br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class=""><div class=""><div class="">
<div dir="auto" style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none;" class=""><div class="">Pauli<br class="">-- <br class="">Dr Paul Dale | Distinguished Architect | Cryptographic Foundations <br class="">Phone +61 7 3031 7217<br class="">Oracle Australia</div><div class=""><br class=""></div></div><br class=""><br class="">
</div>
<div class=""><br class=""><blockquote type="cite" class=""><div class="">On 28 Jul 2020, at 6:19 am, Thomas Dwyer III <<a href="mailto:tomiii@tomiii.com" target="_blank" class="">tomiii@tomiii.com</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class=""><div class="">Hi all,</div><div class=""><br class=""></div><div class="">I'm replacing OpenSSL 1.0.2 with OpenSSL 3.0 in an embedded environment with very limited flash space. We need and use libcrypto and libssl but we have no need for the openssl binary. To date it was never necessary to ship this utility in our product. Now with OpenSSL 3.0 it appears the only way to get FIPS support is to run "openssl fipsinstall ..." to create a FIPS config file to be included by the main config file. However, at nearly 1MB in size this binary is prohibitively large.</div><div class=""><br class=""></div><div class="">I am able to reproduce the output of "openssl fipsinstall ..." with a (considerably smaller) standalone tool that links with libcrypto and generates HMAC-SHA256 (using FIPS_KEY_STRING from fipskey.h) but I'm unclear on what the actual FIPS requirements are for this. Would I still be considered FIPS compliant if I use my own standalone tool instead of the openssl binary to generate the FIPS config? I presume I don't need to bother with the self-test callback and that it only matters whether or not OSSL_PROVIDER_load(NULL, "fips") succeeds?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Tom.III</div><div class=""><br class=""></div></div>
</div></blockquote></div><br class=""></div></div></blockquote></div></div>
</div></blockquote></div><br class=""></div></body></html>