<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Michael Curran wrote:</div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div class="hmmessage" style="font-size: 10pt; font-family: Tahoma; "><div dir="ltr">Are there any potential known issues with stunnel being compiled using openssl 1.0.1 build and leaving the local system binaries at 0.9.8k <div><br></div><div>Do you know of any way to test this for any incompatibilities? This was not my design, Im just being asked to support it and Im looking to make sure this method is not going to cause anything unusual.</div></div></div></span></blockquote></div><br><div>Generally (depending on the version of stunnel) it shouldn't work, as some API functions only available in a new versions of the OpenSSL library will not be exported by an old library. Even if you're able to start stunnel, runtime problems are expected.</div><div><br></div><div>If your problem is that you can't upgrade your OS - there is a simple workaround. Just replace:</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>/your_dir/bin/stunnel /your_dir/etc/stunnel/stunnel.conf</div><div>with:</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>LD_LIBRARY_PATH=/your_dir/lib/ /your_dir/bin/stunnel /your_dir/etc/stunnel/stunnel.conf</div><div>where /your_dir/lib/ is where your OpenSSL 1.0.1 shared libraries are installed.</div><div><br></div><div>Mike</div></body></html>