<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 05.03.2018 10:46, Alan Dean wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANLpu=tr34JrQRuXX1ihGUVq7-hyq8uTcVZ2U2Fzse8s3U=jJw@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">Question 1: Is it even feasible to make the FIPS
mode always enabled for the whole OpenSSL library (i.e. for both
libcrypto and libssl), so that most the applications which
dynamically linked to libcrypto and libssl will be automatically
use OpenSSL FIPS mode without the need of changes to add the
FIPS_mode_set invocation (with some exception such as OpenSSH
which may still need some fixes). (Assuming from certification's
perspective we are ok if we may these changes)
<div><br>
</div>
<div><br>
</div>
<div>Question 2: If the above idea is feasible, where in the
OpenSSL library will be the best entry to invoke FIPS_mode_set
API, so that we can make the whole OpenSSL library always in
FIPS mode? Any potebtial issues for this solution?</div>
<div><br>
</div>
<div><br>
</div>
<div>Any suggestions will be greatly appreciated.</div>
<div><br>
</div>
</div>
<fieldset class="mimeAttachmentHeader"></fieldset>
</blockquote>
<br>
<br>
The optimal location for inserting the FIPS_mode_set(1) call is
probably OPENSSL_init() (openssl-1.0.2/crypto/o_fips.c), see code
snippet below.<br>
<br>
void OPENSSL_init(void)<br>
{<br>
static int done = 0;<br>
if (done)<br>
return;<br>
done = 1;<br>
#ifdef OPENSSL_FIPS<br>
FIPS_set_locking_callbacks(CRYPTO_lock, CRYPTO_add_lock);<br>
# ifndef OPENSSL_NO_DEPRECATED<br>
FIPS_crypto_set_id_callback(CRYPTO_thread_id);<br>
# endif<br>
FIPS_set_error_callbacks(ERR_put_error, ERR_add_error_vdata);<br>
FIPS_set_malloc_callbacks(CRYPTO_malloc, CRYPTO_free);<br>
RAND_init_fips();<br>
FIPS_mode_set(1); <<< ENABLE FIPS MODE HERE
<<<<br>
#endif<br>
#if 0<br>
fprintf(stderr, "Called OPENSSL_init\n");<br>
#endif<br>
<br>
<br>
However, I am sceptical whether this approach will be accepted,
because there are (at least) two potential problems:<br>
<br>
* Normally, it is mandatory to check the result of FIPS_mode_set()
or FIPS_mode() to ensure that the FIPS initialization succeeded.
However, an application which is not FIPS-aware won't check the
result.<br>
* It can happen that applications which have their own configuration
and enable/disable FIPS mode explicitely, call FIPS_mode_set(0)
afterwards.<br>
<br>
<br>
HTH,<br>
Matthias<br>
<br>
<br>
</body>
</html>