Help linking native addon to openssl on Node.js - And general guidance on how to correctly do that

41 views
Skip to first unread message

Jonathan Cardoso

unread,
Oct 4, 2018, 11:57:31 AM10/4/18
to nodejs
I have an issue that I cannot for the love of me find a solution, I will post it here too for extra visibility: https://github.com/nodejs/node-gyp/issues/1559

The main problem is that libcurl (which my addon is built against) seems to use Node.js symbols for OpenSSL, instead of using the one it was built with.

From what I could test, it only occurs with Node.js 10, on 8 it works correctly. on linux it seems to work correctly, 

I would love some help or guidance there, and also some help on the correct way to do that, since I'm pretty sure I'm not doing it right.

This is currently causing some segfaults, since zlib 1.7, which is the one being used, is not compatible with OpenSSL v1.1.0h, the one shipped with Node.js 10.

I know that if upgrade zlib to 1.8 the problem would be resolved, but I still think that there is something wrong there, since it does feel right to use the OpenSSL from Node.js.

Jonathan Cardoso

unread,
Oct 4, 2018, 12:15:41 PM10/4/18
to nodejs
Where I say `zlib` read `libssh`
Reply all
Reply to author
Forward
0 new messages