<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">You might want to check what strerror_r gives you, rather than strerror, since on GCC platforms that's what OpenSSL uses.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Also, OpenSSL builds its table of error strings at startup (or, for older versions, when you tell it to). It's conceivable an application's NLS settings changed between the time when OpenSSL built its table and the time
when the error occurred, which could result in different text from OpenSSL and from a strerror or strerror_r at the point of failure.<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> openssl-users <openssl-users-bounces@openssl.org> on behalf of Jakob Bohm via openssl-users <openssl-users@openssl.org><br>
<b>Sent:</b> Monday, November 26, 2018 11:13:35 AM<br>
<b>To:</b> openssl-users@openssl.org<br>
<b>Subject:</b> Re: [openssl-users] error message oddity</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On 25/11/2018 22:30, Viktor Dukhovni wrote:<br>
>> On Nov 25, 2018, at 4:23 PM, Jeremy Harris <jgh@wizmail.org> wrote:<br>
>><br>
>> That isn't the package name, it is text defined in openssl/opensslv.h<br>
> That happens when "OPENSSL_FIPS" is defined:<br>
><br>
> # define OPENSSL_VERSION_NUMBER 0x101000b0L<br>
> # ifdef OPENSSL_FIPS<br>
> # define OPENSSL_VERSION_TEXT "OpenSSL 1.1.0k-fips-dev xx XXX xxxx"<br>
> # else<br>
> # define OPENSSL_VERSION_TEXT "OpenSSL 1.1.0k-dev xx XXX xxxx"<br>
> # endif<br>
><br>
> Given no FIPS for 1.1.x, perhaps that "#ifdef" should be "#if 0". With<br>
> 1.1.x the "Configure" arguments should not mention "fips".<br>
><br>
A better solution would be to have a separate part of the 1.1.0/1.1.1<br>
headers error out hard (with #error) if attempting to build with<br>
OPENSSL_FIPS defined.<br>
<br>
This would preserve all the FIPS-related stuff (such as the above<br>
version naming code) for when a FIPS module for 1.1.x is provided,<br>
while leaving the blocking of accidental miscompilation in a clear<br>
location having no other effects.<br>
<br>
Enjoy<br>
<br>
Jakob<br>
-- <br>
Jakob Bohm, CIO, Partner, WiseMo A/S. <a href="https://www.wisemo.com">https://www.wisemo.com</a><br>
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10<br>
This public discussion message is non-binding and may contain errors.<br>
WiseMo - Remote Service Management for PCs, Phones and Embedded<br>
<br>
-- <br>
openssl-users mailing list<br>
To unsubscribe: <a href="https://mta.openssl.org/mailman/listinfo/openssl-users">
https://mta.openssl.org/mailman/listinfo/openssl-users</a><br>
</div>
</span></font></div>
</body>
</html>