[rescue] istatserverlinux part - Re: problems compiling istatd and/or Bjango istatserverlinux on Solaris 11.3

Jerry Kemp sun.mail.list47 at oryx.us
Mon May 21 14:22:48 CDT 2018


Hello Jonathan,

OK, here is the default output from Solaris 11.3.  Seems it ships with 1.0.1.p

===============================================
/usr/local/src/i/istatd-0.5.8 603 # openssl version

OpenSSL 1.0.1p 9 Jul 2015

/usr/local/src/i/istatd-0.5.8 604 #

===============================================

Not sure how to determine if elliptic curve cryptography has been disabled.  Will need to read up on that on.

It seems that if I understand your comments correctly, a compile of a current OpenSSL, then pointing my compile towards that 
installation, should fix my compile issue of the Bjango istatserverlinux, or, minimally, get me to the next issue.

Thank you for the reply,

Jerry



On 21/05/18 13:59, Jonathan Patschke wrote:
> On Mon, 21 May 2018, Jerry Kemp wrote:

>> main.cpp: In function ``SSL_CTX* InitServerCTX()'':
>> main.cpp:328:5: error: ``EC_KEY'' was not declared in this scope
>>     EC_KEY *ecdh = EC_KEY_new_by_curve_name(NID_X9_62_prime256v1);
>>     ^
>> main.cpp:328:13: error: ``ecdh'' was not declared in this scope
>>     EC_KEY *ecdh = EC_KEY_new_by_curve_name(NID_X9_62_prime256v1);
>>             ^
>> main.cpp:328:65: error: ``EC_KEY_new_by_curve_name'' was not declared in this scope
>>     EC_KEY *ecdh = EC_KEY_new_by_curve_name(NID_X9_62_prime256v1);
>>                                                                 ^
>> main.cpp:335:21: error: ``EC_KEY_free'' was not declared in this scope
>>     EC_KEY_free(ecdh);
> 
> Your OpenSSL is either too old, or has elliptic curve cryptography
> disabled.  I just checked on a Solaris 11.3 box, and it doesn't have that
> API call.  You'll need at least 1.0.2 (Solaris ships with 1.0.0).
> 
> The world of POSIX SSL/TLS is even more of a dumpster fire than usual
> right now, with the API breakages in OpenSSL 1.0 -> 1.1 and all the
> competing forks (LibreSSL et al) compatibly breaking their APIs at
> different points in development.


More information about the rescue mailing list