On Tue, Jul 22, 2008 at 12:12 PM, The Foxes <[EMAIL PROTECTED]> wrote:
...
> I've compiled the latest openSSL with the ZLIB option (I think that it
> is included by default anyway). That made no difference.
Are you sure you linked stunnel against the libssl *and* the libcrypto
from that? Remember that ld prefers shared library to static ones, so
if you only compiled a static libssl and libcrypto then you'll only
get them if you explicitly tell ld to use them, either by including
the full paths to the lib*.a files in the link or by putting
-Wl,-Bstatic and -Wl,-Bdynamic around the -lssl -lcrypto.
("Other solutions are possible; please show your work for full credit.")
> I tried compiling the latest stunnel but got a lot of errors which
> seemed to be due to missing functions. I added a #include or two to the
> source and got rid of some of the errors, but not all. I'm not that hot
> on this stuff so I'm getting a bit stuck on this route.
There are patches in /usr/ports/security/stunnel/patches/, did you try
applying them or seeing what issues they work around?
> Is there an easy way to tell if zlib has been compiled into openSSL and
> is working?
The libcrypto in OpenBSD-current (and presumably earlier, I haven't
checked) does not include the zlib compression method:
$ nm /usr/lib/libcrypto.so.13.0 | grep zlib_method
2001cda0 d zlib_method_nozlib
$
If zlib compression was included, it wouldn't have the "_nozlib" suffix.
Philip Guenther
