Again there’s a new Version of OpenSSL, this time only the 1.0 main branch was affected by a security flaw:
Direct Download
for Win32: http://indy.fulgan.com/SSL/openssl-1.0.0e-i386-win32.zip
for Win64: http://indy.fulgan.com/SSL/openssl-1.0.0e-x64_86-win64.zip
As usual you’ll find the ReadMe, Hashes and the OpenSSL binary inside of the ZIP.
Cheers,
Arvid
It works but there is a warning as follows.
WARNING: can’t open config file: /usr/local/ssl/openssl.cnf
that’s ok. It means that the OpenSSL.exe includes a hardcoded path for searching it’s settings. If the settings are not found, OpenSSL uses it’s defaults. So this behavior is normal for the OpenSSL.exe under Windows.
Is there a need for these customized DLL’s any more? I thought using the Open SSL library DLL’s now worked… (like from http://www.slproweb.com/products/Win32OpenSSL.html) Are there customizations specific to Indy other than version resource?
No “need” for it anymore, that’s right – but, and that’s a large but, our own DLLs do not need any external libraries.
If you use slproweb’s you’ll have to install MS VC runtime dlls on the target.
We still support Win2000 out-of-the-box and we don’t have that requirement.
Cheers,
Arvid