Centos7.3 Cannot get required symbol EC_KEY_set_public_key_affine_coordinates from libssl

[xinschen]

Centos7.3 Cannot get required symbol EC_KEY_set_public_key_affine_coordinates from libssl
openssl info
OpenSSL 1.0.2k-fips 26 Jan 2017

Referenced to ”#1930" and Upgrade openssl to version 1.1.0g，but did not solve

dotnet --info

dotnet new -h

[karelz]

@tmds @bartonjs can you please help route the question?

[karelz]

@bartonjs ping?

[bartonjs]

@xinschen .NET Core 2.1 doesn't use OpenSSL 1.1, so updating the 1.1 package wouldn't do anything. Updating to the newest openssl-libs 1.0 package would be the thing to try; or to move from CentOS 7.3 (12 Dec 2016) to 7.5 (10 May 2018) or 7.6 (3 Dec 2018).

[xinschen]

@bartonjs Already upgraded, but not resolved

[karelz]

@bartonjs can you please help troubleshoot it further or route it appropriately? Thanks!

[karelz]

@bartonjs ping

[omajid]

AFAIK, no current stable/public release of .NET Core supports OpenSSL 1.1. So when openssl version -a says OpenSSL 1.1.1a or when ldd says libssl.so.1.1, that's not very helpful for fixing this issue.

We want to know what rpm -q openssl and rpm -q openssl-libs. If that says "1.1", we need to remove those packages and install (actually downgrade to) OpenSSL 1.0 on CentOS. An strace dotnet new console would be useful after OpenSSL 1.0 has been installed to find out what fails and when.

[karelz]

Looks like we do not have actionable information, closing.
Please let me know if I made a mistake. Thanks!

[omajid]

Just as an FYI: recent releases of .NET Core 2.x should support OpenSSL 1.1 (as well as OpenSSL 1.0) out of the box. If this issue still occurs, please re-open this bug.