Re: Package Request: .NET Core

[hatf0 <hatf0@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1723 bytes --]

New comment by hatf0 on void-packages repository

https://github.com/void-linux/void-packages/issues/10773#issuecomment-630237620

Comment:
A major problem I'm (personally) running into with .NET Core:
`Cannot get required symbol d2i_ASN1_type_bytes from libssl`
I've double checked on my machine (with latest libssl), but...
```
nm -anD /usr/lib/libssl.so | grep 'ASN1'
                 U PEM_ASN1_read
                 U PEM_ASN1_read_bio
                 U PEM_ASN1_write
                 U PEM_ASN1_write_bio
000000000002e250 T SSL_use_certificate_ASN1
000000000002e4f0 T SSL_use_RSAPrivateKey_ASN1
000000000002e710 T SSL_use_PrivateKey_ASN1
000000000002ea40 T SSL_CTX_use_certificate_ASN1
000000000002ed00 T SSL_CTX_use_RSAPrivateKey_ASN1
000000000002ef50 T SSL_CTX_use_PrivateKey_ASN1
```

So, still looks like the same compatibility issue (as posted above) with LibreSSL remains... and the developers are intentionally going out of their way to avoid creating a compatibility layer with LibreSSL as much as possible:
>On macOS the system libraries do not support AES-CCM or AES-GCM for 3rd party code, so the   AesCcm and AesGcm classes use OpenSSL for support. Users on macOS need to obtain an appropriate copy of OpenSSL (libcrypto) for these types to function, and it must be in a path that the system would load a library from by default. Obtaining OpenSSL from a package manager, such as Homebrew, is recommended (but not required). The libcrypto.0.9.7.dylib and libcrypto.0.9.8.dylib libraries included in macOS are from older versions of OpenSSL, and will not be used. The libcrypto.35.dylib, libcrypto.41.dylib, and libcrypto.42.dylib are LibreSSL, and will not be used.

What a shame...