You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "BewareMyPower (via GitHub)" <gi...@apache.org> on 2023/02/23 09:41:33 UTC

[GitHub] [pulsar-client-node] BewareMyPower commented on pull request #300: [fix] MacOS tls get certs failed.

BewareMyPower commented on PR #300:
URL: https://github.com/apache/pulsar-client-node/pull/300#issuecomment-1441456029

   > Is there a way to release two versions of the package? One with statically linked libraries and one with dynamic linking?
   
   If we linked to OpenSSL dynamically, we have to link other dependencies dynamically too. It would require users to install all the dependencies (e.g. Boost, Protobuf, etc.) into their systems. At the moment, I cannot think of a way to fix this issue.
   
   I'm wondering if we can get the default CA cert bundle location via the Node.js code and then set it as the default `tlsTrustCertsFilePath` config?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org