Not able to connect to ssh .

when i run command ssh username@remoteserver

i get the follwing error

ld.so.1: ssh: fatal: relocation error: file /usr/bin/ssh: symbol SUNWcry_installed: referenced symbol not found
Killed

libsocket.so.1 => /lib/libsocket.so.1
libnsl.so.1 => /lib/libnsl.so.1
libz.so.1 => /usr/lib/libz.so.1
libcrypto.so.0.9.7 => /opt/symas/lib/libcrypto.so.0.9.7
libgss.so.1 => /usr/lib/libgss.so.1
libc.so.1 => /lib/libc.so.1
libmp.so.2 => /lib/libmp.so.2
libmd.so.1 => /lib/libmd.so.1
libscf.so.1 => /lib/libscf.so.1
libdl.so.1 => /lib/libdl.so.1
libcmd.so.1 => /lib/libcmd.so.1
libdoor.so.1 => /lib/libdoor.so.1
libuutil.so.1 => /lib/libuutil.so.1
libgen.so.1 => /lib/libgen.so.1
libm.so.2 => /lib/libm.so.2
/platform/SUNW,Sun-Fire-T200/lib/libc_psr.so.1
/platform/SUNW,Sun-Fire-T200/lib/libmd_psr.so.1

I guess, it's because ssh is loading libcrypto from /opt/symas/lib instead of the solaris version of this library.

What does

echo $LD_LIBRARY_PATH
crle

The dynamic linker starts to look for dynamic libraries in the directories given in $LD_LIBRARY_PATH, then in the program's runpath and finally in the default path defined with crle.

Because symas seems to use a library with the same name as a solaris system library, all commands find the symas version instead of the solaris version.

You can insert /lib:/usr/lib at the beginning of LD_LIBRARY_PATH. That would make ssh and probably other solaris commands find the solaris version of libcrypto.

But you have to check, if this has any unwanted side effects on symas commands (if they can't deal with the solaris version of libcrypto).

Hi Thanks for the help . I found the following SSH is using

stat64("/usr/openwin/lib/libcrypto.so.0.9.7", 0xFFBFF208) Err#2 ENOENT 
stat64("/usr/sfw/lib/libcrypto.so.0.9.7", 0xFFBFF208) = 0 
resolvepath("/usr/sfw/lib/libcrypto.so.0.9.7", "/usr/sfw/lib/libcrypto.so.0.9.7", 1023) = 31 
open("/usr/sfw/lib/libcrypto.so.0.9.7", O_RDONLY) = 3 
stat64("/usr/openwin/lib/libcrypto_extra.so.0.9.7", 0xFFBFEEC0) Err#2 ENOENT 
stat64("/usr/sfw/lib/libcrypto_extra.so.0.9.7", 0xFFBFEEC0) = 0 
resolvepath("/usr/sfw/lib/libcrypto_extra.so.0.9.7", "/usr/sfw/lib/libcrypto_extra.so.0.9.7", 1023) = 37 
open("/usr/sfw/lib/libcrypto_extra.so.0.9.7", O_RDONLY) = 3 
stat64("/usr/openwin/lib/libcrypto_extra.so.0.9.7", 0xFFBFE7B8) Err#2 ENOENT 
 
following crypto packages are installed on this system 


system      SUNWcry                          Crypt Utilities 
system      SUNWcryr                         Solaris Root Crypto

Looks good. ssh loads the solaris libcrypto library from /usr/sfw/lib (not /usr/lib as I assumed erroneously before).

This is, what ldd /usr/bin/ssh should look on Solaris 10u8 (x86):

        libsocket.so.1 =>        /lib/libsocket.so.1
        libnsl.so.1 =>   /lib/libnsl.so.1
        libz.so.1 =>     /usr/lib/libz.so.1
        libcrypto.so.0.9.7 =>    /usr/sfw/lib/libcrypto.so.0.9.7
        libgss.so.1 =>   /usr/lib/libgss.so.1
        libc.so.1 =>     /lib/libc.so.1
        libmp.so.2 =>    /lib/libmp.so.2
        libmd.so.1 =>    /lib/libmd.so.1
        libscf.so.1 =>   /lib/libscf.so.1
        libcmd.so.1 =>   /lib/libcmd.so.1
        libdoor.so.1 =>  /lib/libdoor.so.1
        libuutil.so.1 =>         /lib/libuutil.so.1
        libgen.so.1 =>   /lib/libgen.so.1
        libcrypto_extra.so.0.9.7 =>      /usr/sfw/lib/libcrypto_extra.so.0.9.7
        libm.so.2 =>     /lib/libm.so.2

        libsocket.so.1 =>        /lib/libsocket.so.1
        libnsl.so.1 =>   /lib/libnsl.so.1
        libz.so.1 =>     /usr/lib/libz.so.1
        libcrypto.so.0.9.7 =>    /usr/sfw/lib/libcrypto.so.0.9.7
        libgss.so.1 =>   /usr/lib/libgss.so.1
        libc.so.1 =>     /lib/libc.so.1
        libmp.so.2 =>    /lib/libmp.so.2
        libmd5.so.1 =>   /lib/libmd5.so.1
        libscf.so.1 =>   /lib/libscf.so.1
        libcmd.so.1 =>   /lib/libcmd.so.1
        libdoor.so.1 =>  /lib/libdoor.so.1
        libuutil.so.1 =>         /lib/libuutil.so.1
        libm.so.2 =>     /lib/libm.so.2
        /platform/SUNW,Sun-Fire-T200/lib/libc_psr.so.1

As an aside, Symas's code is always linked with proper embedded runpaths so there is no need to put /opt/symas/lib in an LD_LIBRARY_PATH value or even in an ldconfig file. The only exception to this is if some other software wants to use Symas's libraries (which is perfectly appropriate) and wasn't linked with runpaths.