|laziness, impatience, and hubris|
need to fix my installation of IO::Socket::SSL, but how?by ted.byers (Monk)
|on Nov 28, 2012 at 21:08 UTC||Need Help??|
ted.byers has asked for the
wisdom of the Perl Monks concerning the following question:
In the docs, I read, under limitations, "IO::Socket::SSL uses Net::SSLeay as the shiny interface to OpenSSL, which is the shiny interface to the ugliness of SSL. As a result, you will need both Net::SSLeay and OpenSSL on your computer before using this module."
The question is, what does this really require? For example, I have, on the machines in question, openssl. And I run it from the commandline, either in it's install/bin directory, or by specifying the full path to the openssl binary. I assume that isn't good enough for IO::Socket::SSL, and that, at a minimum I need to add the path to the openssl binary to the system path (this is on Windows).
However, I am uncertain as to whether or not it also requires the path and file name for the configuration file I normally use for openssl. The openssl binary, on Windows, uses a unix path, beginning with '/usr' to search for the configuration file, and obviously that path does not exist on Windows. Therefore, for any real use, I have to pass a commandline argument to openssl to tell it where the configuration file is. How, then, do I tell IO::Socket::SSL where openssl is and where it's configuration file is?
Please note, I have never used IO::Socket::SSL directly, but I need it in order for LWP::UserAgent to connect to secure sites.