linuxdcpp-team team mailing list archive

[eMTee <question229141@xxxxxxxxxxxxxxxxxxxxx>]

Question #229141 on ADCH++ changed:
https://answers.launchpad.net/adchpp/+question/229141

    Status: Open => Answered

eMTee proposed the following answer:
Googling the error message "WARNING: can’t open config file: /usr/local/ssl/openssl.cnf" gives the solution of the problem. In the recent builds they probably changed the default value of the OPENSSL_CONF  variable from C:\Program Files\OpenSSL\bin to something else hence it doesn't work anymore without setting up that env variable.
And obiviously by default they don't check for that .cfg file the directory OpenSSL. exe started from, that'd be far too user friendly I suppose...

I updated the docs in the website, made some things more clear about
setting up the adchpp.xml and ADCS. I also added a link to the basic
guide pointing to a new Windows cert gen script that tries to cope with
the Win32OpenSSL installation path's. Now it should work when OpenSSL
resides in the path offered in the installer by default as well as if
it's installed to C:\Program Files\OpenSSL

-- 
You received this question notification because you are a member of
Dcplusplus-team, which is an answer contact for ADCH++.