Err, wouldn't that be a bad idea, when different applications might want to use different versions of OpenSSL?
We frequently get problems with our application, due to other "rogue" applications that put their OpenSSL ddls into the standard %PATH%, for example in the system32 directory, which can then take precedence over our installed versions. Essentially, for a commonly installed third-party product like OpenSSL, the dlls that are used by a particular application should be installed in a directory belonging to that application. And the application, or the installation program of that application, should control the %PATH% used by that application, so that the correct version is used. G. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Filip Palian via RT Sent: 04 April 2008 14:41 Cc: openssl-dev@openssl.org Subject: [openssl.org #1660] Request for feature, all Windows systems, all OpenSSL versions. Dear Sir/Maddam, More and more programs uses OpenSSL. In Windows systems it's often necessarily/* */to manually copy libeay32.dll and libssl32.dll into some directory. Moreover, this directory should be within %PATH% environment variable. In my opinion it would be a good idea, to add OpenSSL installation directory into the %PATH% variable by the installer. I'm sure it would make people lifes easier. Obviously if there are no technical issues against it. Thank you very much for your work! Best regards, Filip Palian. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
