Date: Wed, 5 Mar 2003 13:55:14 -0800 (PST) From: Julian Elischer <julian@elischer.org> To: hackers@freebsd.org Subject: ssh/ssl linkage Message-ID: <Pine.BSF.4.21.0303051350510.61509-100000@InterJet.elischer.org>
next in thread | raw e-mail | index | archive | help
OpenSSH uses openssl to a great extent, however when you do
ldd ssh
you get:
libssh.so.2 => /usr/lib/libssh.so.2 (0x28078000)
libcrypto.so.2 => /usr/lib/libcrypto.so.2 (0x280a9000)
libutil.so.3 => /usr/lib/libutil.so.3 (0x28161000)
libz.so.2 => /usr/lib/libz.so.2 (0x2816a000)
libc.so.4 => /usr/lib/libc.so.4 (0x28177000)
or in earlier versions:
libcrypto.so.2 => /usr/lib/libcrypto.so.2 (0x2808a000)
libutil.so.3 => /usr/lib/libutil.so.3 (0x28143000)
libz.so.2 => /usr/lib/libz.so.2 (0x2814b000)
libc.so.4 => /usr/lib/libc.so.4 (0x28158000)
so my question is:
how is the connection made to libssl?
is it via libcrypto?
is it statically built into the ssh binary?
If I upgrade openssl due to teh security upgrade,
should I recompile ssh as well?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0303051350510.61509-100000>