openssh unix dev - Jan 2003 - OpenSSH & OpenSSL directory location problem.

Problem: scp does not work with custom openssl library location

OpenSSH & OpenSSL directory location problem.

checking whether snprintf correctly terminates long strings... yes
checking whether getpgrp requires zero arguments... yes
checking OpenSSL header version... 90608f (OpenSSL 0.9.6h [engine]  5 
Dec 2002)
checking OpenSSL library version... 90608f (OpenSSL 0.9.6h [engine]  5 
Dec 2002)
checking whether OpenSSL's headers match the library... yes
checking for crypt in -lcrypt... yes
checking whether OpenSSL's PRNG is internally seeded... yes
checking for ls... /bin/ls

As you can see it finds it just fine by using the GCC variables below.

             Host: i686-pc-linux-gnu
         Compiler: gcc
   Compiler flags: -g -O2 -Wall -Wpointer-arith -Wno-uninitialized
Preprocessor flags: -I/vapp/include
     Linker flags: -L/vapp/lib
        Libraries:   -lutil -lz -lnsl  -lcrypto -lcrypt

# GCC Variables (works with all programs, except OpenSSH.
export C_INCLUDE_PATH=/vapp/include:/usr/X11R6/include
export CPLUS_INCLUDE_PATH=/vapp/include:/usr/X11R6/include
export LIBRARY_PATH=/vapp/lib
# So, also included these:
export LDFLAGS=-L/vapp/lib
export CPPFLAGS=-I/vapp/include
# Also tried this option.
 --without-rpath         Disable auto-added -R linker paths

# Yet, with every one of these, I get this error with SCP ONLY (SSH=FINE)
$ scp war at p300:/home/war/ping6 .
war at p300's password:
scp: error while loading shared libraries: libcrypto.so.0.9.6: cannot open
shared object file: No such file or directory

Why is this? The daemon (sshd) works fine with no errors of the sort.
Yet, when doing an SCP I get the error as defined above.

[war at war war]$ ssh p300
war at p300's password:
Last login: Fri Jan 31 13:39:58 2003 from 192.168.168.24
war at p300:~$

( no problems )

control-d
Connection to p300 closed.
[war at war war]$

Connection to p300 closed.
[war at war war]$ scp war at p300:/home/war/ping6 .
war at p300's password:
scp: error while loading shared libraries: libcrypto.so.0.9.6: cannot 
open shared object file: No such file or directory
[war at war war]$

war at p300:~$ ldd `which sshd`
       libutil.so.1 => /lib/libutil.so.1 (0x40016000)
       libz.so.1 => /vapp/lib/libz.so.1 (0x40019000)
       libnsl.so.1 => /lib/libnsl.so.1 (0x40027000)
       libcrypto.so.0.9.6 => /vapp/lib/libcrypto.so.0.9.6 (0x4003c000)
       libcrypt.so.1 => /lib/libcrypt.so.1 (0x40109000)
       libc.so.6 => /lib/libc.so.6 (0x40136000)
       libdl.so.2 => /lib/libdl.so.2 (0x40259000)
       /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
war at p300:~$

war at p300:~$ ldd `which sshd`
       libutil.so.1 => /lib/libutil.so.1 (0x40016000)
       libz.so.1 => /vapp/lib/libz.so.1 (0x40019000)
       libnsl.so.1 => /lib/libnsl.so.1 (0x40027000)
       libcrypto.so.0.9.6 => /vapp/lib/libcrypto.so.0.9.6 (0x4003c000)
       libcrypt.so.1 => /lib/libcrypt.so.1 (0x40109000)
       libc.so.6 => /lib/libc.so.6 (0x40136000)
       libdl.so.2 => /lib/libdl.so.2 (0x40259000)
       /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
war at p300:~$ echo $PATH
/vapp/bin:/vapp/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
war at p300:~$ echo $LD_LIBRARY_PATH
/vapp/lib:/lib:/usr/lib:/usr/X11R6/lib
war at p300:~$

So question = why does it work fine with sshd and not scp?

jpiszcz wrote:
> war at p300's password:
> scp: error while loading shared libraries: libcrypto.so.0.9.6: cannot
> open shared object file: No such file or directory
[snip]
> So question = why does it work fine with sshd and not scp?
The error is coming from the scp running at the other end of the ssh
connection.  Maybe LD_LIBRARY_PATH is different when logging on
non-interactively?  

Try ssh user at host '/bin/echo $LD_LIBRARY_PATH'

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

On Fri, 31 Jan 2003, jpiszcz wrote:
> Problem: scp does not work with custom openssl library location
>
> As you can see it finds it just fine by using the GCC variables below.
>
>              Host: i686-pc-linux-gnu
>          Compiler: gcc
>    Compiler flags: -g -O2 -Wall -Wpointer-arith -Wno-uninitialized
> Preprocessor flags: -I/vapp/include
>      Linker flags: -L/vapp/lib
>         Libraries:   -lutil -lz -lnsl  -lcrypto -lcrypt
This isn't fine, there should be a -R/vapp/lib in the linker flags.  Without
-R you need to set LD_LIBRARY_PATH at run time.  LD_LIBRARY_PATH is
really a debug aid and should be avoided if at all possible.

Adding a -L without a corresponding -R is probably a bug in the configure
script - I don't know anything about autoconf so I don't know if it is
autoconf or the template that has needs to be updated.

Alternates on Linux are adding /vapp/lib to /etc/ld.so.config.  On Solaris 8
use crle(1m).

If you need to make the binaries relocatable and have the lib dir at a
set location from the bin dir: eg ..../bin/scp and ..../lib/libcrypto.so then
you can use the $ORIGIN variable for -R on Solaris (and I believe on Linux
as well).

-- 
Darren J Moffat

war at p300:~/openssh-3.5p1$ ./configure --prefix=/app/openssh-3.5p1 
--with-md5-passwords --with-ssl 
--with-privsep-path=/app/openssh-3.5p1/var/empty 
--with-privsep-user=sshd ; make ; make install

standard config as before, but added path to /etc/ld.so.conf, however 
I've never had to add a path to here to get a certain program/app to 
work before..

So the ld.so.conf provides the environment for applications which do not 
provide the environment by default..


Darren J Moffat wrote:
>On Fri, 31 Jan 2003, jpiszcz wrote:
>
>  
>
>>At the end of make:
>>gcc: unrecognized option `-R/vapp/lib'
>>    
>>
>
>I think the linker (ld) on Linux needs a space in between the -R and the /
>so try:  -R /vapp/lib.  If that doesn't work try -rpath /vapp/lib
instead.
>
>  
>