> Is there any way to turn this off, when building OpenSSL? I'm not sure if there is a configuration switch like no-conf. `Configure` is not much help here since it silently consumes bad options.
If interested, I believe you can change the behavior at runtime with `OPENSSL_no_config`. See https://www.openssl.org/docs/crypto/OPENSSL_config.html. The issue you might run into is contention among the various components using OpenSSL. That is, your lib does not want to read the conf file, while another competing lib wants to read a conf file. You might end up in a mini configuration war. Jeff On Mon, Dec 1, 2014 at 3:47 PM, Tanel Lebedev <tanel.lebe...@gmail.com> wrote: > Hi everybody, > > I'm building and packaging OpenSSL as a third party library in my app. I > also include a certificate bundle with it. > > Now it seems that the OpenSSL library that is packaged with my app, tries to > pick up users local OpenSSL settings (/some/path/openssl.cnf). > > Is there any way to turn this off, when building OpenSSL? I'd like the > OpenSSL library not to poke around on users machine, only use the > certificate bundle I've specified etc. > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
