The simpler variant of this question, vis how to tell openssl where the configuration file is, is a FAQ, and I have seen it countless times over the past few years, as a result of my searches using Google. However, my present situation is a bit different.
I am developing perl programs that must make SSL connections to secure servers, and some of my programs that do this have been working fine for as much as five years. However, a couple of them have started to fail with a handful of secure sites that have new 'extended validation' certificates. This is the only consistent difference between those sites that I can still connect to and those that I can't. For those who don't know, web programming using Perl involves a number of complicated packages, most of which are written in perl, and unfortunately, the perl package that is responsible for SSL/TLS connections is buried deep in the bowels of the most complex of these, and it requires that openssl is installed. I do have openssl installed (this is on Windows (several varieties including WXP, Windows 7 and Windows Server 2008, both 32 bit and 64 bit), but I have not added it's bin directory to the system path (to date, I haven't had to). I know I can ensure my perl programs can find it by adding that path to the system path, but there remains the problem that every time I start openssl from a commandline without passing the path to the configuration file as a commandline argument, it complains that the file couldn't be found is some Unix path I can't remember (but beginning with '/usr').. Hence the question: Is it possible to tell openssl where the configuration file is, e.g. by setting an environment variable, without passing a commandline argument? Thanks Ted ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
