TLS module doesn't load openssl engine

[whocaresk]

• Version: v10.15.1
• Platform: Linux 6e28ec3fedee 4.18.0-15-generic 16-Ubuntu SMP Thu Feb 7 10:56:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
• Subsystem: TLS module

Hello,
I'm having troubles with loading custom OpenSSL engine in TLS module.
OpenSSL outputs correct engine and ciphers.
I've build latest node LTS (v10.15.1) with shared openssl:
./configure --shared-openssl --shared-openssl-includes=/opt/cprocsp/cp-openssl-1.1.0/include --shared-openssl-libname=crypto,ssl,gostengy --shared-openssl-libpath=/opt/cprocsp/cp-openssl-1.1.0/lib/amd64
make && make install
Then, when i'm starting node with openssl-config flag it doesn't load ciphers from gostengy in TLS module, but in crypto module they exists with call
crypto.setEngine('gostengy');
I've seen older issues and following pulls (about 3 years ago) that should fixing this issue, but seems that with newer openssl version something went wrong. #5101
Here is reproduction repo that bootstraps my environment: link

[bnoordhuis]

Expectations management annex disclaimer: if you're not using the bundled openssl, you're basically on your own. That's not a supported configuration, it's mainly for distro vendors.

If you have specific reason to believe it's an issue with Node.js (with suggestions on how to fix it), we could leave this open in case someone is willing to work on it; pull request also welcome, of course. Otherwise it's probably best to move it to nodejs/help.