rworkman |
08-03-2012 10:50 AM |
EDIT: well, I guess I should have refreshed the page before replying, but oh well... :)
First of all, I don't see that here:
Code:
[rworkman@liberty ~]$ ldd /usr/bin/curl
linux-vdso.so.1 (0x00007fff26d82000)
libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f7ae8fc9000)
librt.so.1 => /lib64/librt.so.1 (0x00007f7ae8d95000)
libz.so.1 => /usr/lib64/libz.so.1 (0x00007f7ae8b7f000)
libc.so.6 => /lib64/libc.so.6 (0x00007f7ae87c2000)
libidn.so.11 => /usr/lib64/libidn.so.11 (0x00007f7ae8590000)
liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007f7ae8381000)
libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007f7ae8139000)
libssl.so.1 => /usr/lib64/libssl.so.1 (0x00007f7ae7ed1000)
libcrypto.so.1 => /usr/lib64/libcrypto.so.1 (0x00007f7ae7af5000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7ae78d9000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7ae9222000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f7ae76bf000)
libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f7ae74a4000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f7ae72a0000)
What isn't immediately obvious though is that curl itself isn't even linked to libssl - ldd shows a recursive list of everything that curl is linked against, everything that those things are linked against, and so on. A better list comes from this:
Code:
[rworkman@liberty ~]$ objdump -p /usr/bin/curl | grep NEEDED
NEEDED libcurl.so.4
NEEDED librt.so.1
NEEDED libz.so.1
NEEDED libc.so.6
Now it becomes more clear where the libssl linking is:
Code:
[rworkman@liberty ~]$ objdump -p /usr/lib64/libcurl.so.4 | grep NEEDED
NEEDED libidn.so.11
NEEDED liblber-2.4.so.2
NEEDED libldap-2.4.so.2
NEEDED librt.so.1
NEEDED libssl.so.1
NEEDED libcrypto.so.1
NEEDED libz.so.1
NEEDED libc.so.6
Of course, none of that answers your initial question. Given how ldd(1) behaves, I suspect that you have an old library still iinked to libssl.so.0 - make sure you didn't miss a package.
|