Call for testing: OpenSSH 9.7

[Damien Miller]

On Wed, 6 Mar 2024, The Doctor wrote:

> > > > snapshot.  We're trying to confirm it does in fact fix what you have
> > > > observed.  You will need to apply the patch yourself to a snapshot or
> > > > git HEAD and run "autoreconf" to rebuild configure, then run
> > > > ./configure with your options.
> > > >
> > > >
> > >
> > > Tried it and got
> > >
> > > checking for openssl... /usr/bin/openssl
> > > checking for openssl/opensslv.h... yes
> > > checking OpenSSL header version... 30200020 (OpenSSL 3.2.2-dev )
> > > checking for OpenSSL_version... yes
> > > checking for OpenSSL_version_num... yes
> > > checking OpenSSL library version... 300000e0 (OpenSSL 3.0.14-dev )
> > > checking whether OpenSSL's headers match the library... no
> > > configure: error: Your OpenSSL headers do not match your
> > >         library. Check config.log for details.
> > >                 If you are sure your installation is consistent, you can disable the check
> > >                         by running "./configure --without-openssl-header-check".
> > >                                 Also see contrib/findssl.sh for help identifying header/library mismatches.
> > 
> > That sounds like the runtime linker path problem I described in my
> > first reply.   Is the OpenSSL 3.2.2-dev version of libcrypto in your
> > runtime linker path? I assume that's in /usr/local/lib?  Does
> > /usr/local/bin/openssl actually work?
> 
> This is odd.
> 
> /usr/local/bin/openssl version -a
> ld-elf.so.1: /usr/lib/libssl.so.3: version OPENSSL_3.2.0 required by /usr/local/bin/openssl not found
> 
> 
> It should be reference /usr/local/lib/libssl.so 

This is the same problem Darren described. You have openssl libraries
installed that are not in the runtime linker search path. --with-rpath
will fix this for OpenSSH, but it can't fix the openssl binary you
already have installed.

Your options include (if your system support them) things like adjusting
ld.so.conf or manually setting LD_LIBRARY_PATH.

-d