Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

[Update] A solution has been found:

I'm embedding Node within a browser extension and don't want the user to manually install openssl or even know what it is, I'd rather it was bundled into the Node build or statically linked to files held within the browser extension.

I already know how to disable openssl completely in Node and that solution works, however I'd like to have openssl enabled incase my users require it at some point.

I'm also aware of the --openssl-includes and --openssl-libpath ./configure flags, however they didn't seem to do what I wanted when I pointed them to a directory containing a static build of libssl and crypto – the build failed because it couldn't find the "SSL_library_init" function.

Any ideas how I can do this? If it help, I'm happy with a solution just for OS X for now. I can work out the rest later.

I appreciate the help.

share|improve this question
It's worth noting the export/import restrictions on SSL/cryptography software. If you bundle OpenSSL with your software you may run into legal issues – Smudge Dec 6 '11 at 11:37
Thanks Sam, I'll make sure to look into that once I've found out if this is even possible. – Robin Hawkes Dec 6 '11 at 11:43

A solution has been found via. Ryan Dahl, creator of Node. Basically I just needed to use the new gyp build process that seems to have arrived with the 0.6 versions of Node. Within the options.gypi file that is generated during build you can set the node_use_system_openssl to false and it will use a static library for openssl.

More details:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.