I am using stunnel to tunnel my VNC connection.  As recent as
version 4.12 I have been able to use the libeay32.dll and libssl32.dll
files I created with openssl 0.9.X.X using Msys and Mingw with 
the steps below:<br>



<p>1. I comment out line 910 in the openssl Configure script</p>

2. Create .def for dll's:<br>

perl util/mkdef.pl 32 libeay &gt;
ms/libeay32.def<br>

perl util/mkdef.pl 32 ssleay &gt;
ms/ssleay32.def







<p>3. Execute the openssl configure script<span><br>
</span>./Configure
mingw</p>

<p>4. Execute the make for openssl<br>
make

</p>

5. After the make completes I create the dlls<br>

dllwrap --dllname libeay32.dll
--output-lib libeay32.a --def ms/libeay32.def libcrypto.a -lwsock32 -lgdi32<br>

dllwrap --dllname libssl32.dll
--output-lib libssl32.a --def ms/ssleay32.def libssl.a libeay32.a<br>

<br>

When I place the resulting dlls on the remote machine with version 4.14
installed and establish a VNC connection to machine stunnel crashes and
generates a Dr. Watson error.&nbsp; If I revert back to version 4.12
the dlls I created using the steps above --- everything works.&nbsp; If
I install the 0.9.7i dlls (which come as a part of the 4.14 Win Install
package) everything works.<br>

<br>

I am trying to keep server and clients on the same version of openssl
which is why I have been compling new dlls whenever I have upgraded the
servers.&nbsp; Is there something unique being done in version 4.14
that prevents dlls created with 0.9.8a from being used?<br>

<br>

-- Chris