May 18, 2012

Filed under: Automation,Scripting — Marcus Tettmar @ 9:52 am

I recently wrote a small macro for a customer which does an HTTPRequest via SSL. This requires that OpenSSL is installed. But the customer wanted to know if there was any way of distributing the macro to his users without having to install OpenSSL on all their PCs.

Thanks to our wonderful forums one of our users has already figured out how to do this and it turns out only 2 DLLs are required and can be placed in either the Macro Scheduler program folder, or, in the case of a compiled macro, the exe’s folder.

Adroege says:

I use this solution:

Download the “binaries” from this page as a zip file
http://gnuwin32.sourceforge.net/packages/openssl.htm

Unzip the contents

find the files libeay32.dll (version 0.9.8.8) and libssl32.dll
(version 0.9.8.8) in the Bin folder

Make a copy of libssl32.dll and call it “ssleay32.dll”

Now just deliver all 3 DLL files in the same folder as the
compiled Macro Scheduler EXE
(libeay32.dll libssl32.dll ssleay32.dll)

Using this method, I didn’t have to do any special SSL “install”,
run regsvr32.exe, or do any registry hacks. It just works.

And rullbandspelare responds:

It appears to work with just putting
ssleay32.dll and libeay32.dll in the same folder.

Even I learn stuff from our forums, or at least find answers more quickly. A great resource. Thanks guys.

3 Comments »

  1. I have tried this several times and cannot get this to work. I place the files in the Macro 14 directory where the scripts are saved from MJTnet, but nothing.

    Is there an updated option in any new version that works?

    Comment by Jesse — March 25, 2014 @ 10:40 pm

  2. I think you would need to put them in the Macro Scheduler program folder, not the script folder. In the case of a compiled macro you could put them in the same folder as the .exe

    But if that fails then try installing OpenSSL properly. Make sure you download the Win32 (32 bit) version – Macro Scheduler is 32 bit. Download the recommended 32 bit version from: http://slproweb.com/products/Win32OpenSSL.html

    Comment by Marcus Tettmar — March 27, 2014 @ 10:01 pm

  3. Another possibility is that the required VC++ redistributables or some other runtimes are not installed. Installing the full Win32 OpenSSL package is the recommended method.

    Comment by Marcus Tettmar — March 27, 2014 @ 10:03 pm

RSS feed for comments on this post. TrackBack URL

Leave a comment