OpenSSH 3.2.3p1 incompatibilities between Solaris 7 and 8

From: Ernie Oporto (ernieoporto@yahoo.com)
Date: 06/08/02


From: ernieoporto@yahoo.com (Ernie Oporto)
Date: 7 Jun 2002 15:33:10 -0700

I get this on a Solaris 8 machine that has OpenSSH 3.2.3p1 installed
as compiled on a Solaris 7 machine with openssl-0.9.6d. I thought the
binary compatibility would work for this as it has for all else.

kbar.41:/nj/adm/src/openssh-3.2.3p1# make host-key-force
(cd openbsd-compat && make)
make[1]: Entering directory
`/nj/adm/src/openssh-3.2.3p1/openbsd-compat'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory
`/nj/adm/src/openssh-3.2.3p1/openbsd-compat'
./ssh-keygen -t rsa1 -f /usr/local/etc/ssh_host_key -N ""
ld.so.1: ./ssh-keygen: fatal: relocation error: file
/usr/local/ssl/lib/libcrypto.so.0.9.6: symbol __register_frame_info:
referenced symbol not found
Killed
make: *** [host-key-force] Error 137
kbar.42:/nj/adm/src/openssh-3.2.3p1#

When I try to configure OpenSSH 3.2.3p1 on the Solaris 8 machine, I
get this...
kbar.47:/nj/adm/src/openssh-3.2.3p1# ./configure --enable-shared
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
[...]
checking for getutxline... yes
checking for pututxline... yes
checking for setutxent... yes
checking for utmpxname... yes
checking for getuserattr... no
checking for getuserattr in -ls... no
checking for daemon... no
checking for daemon in -lbsd... no
checking for getpagesize... yes
checking whether snprintf correctly terminates long strings... no
configure: WARNING: ****** Your snprintf() function is broken,
complain to your vendor
checking whether getpgrp requires zero arguments... yes
checking whether OpenSSL's headers match the library... no
configure: error: Your OpenSSL headers do not match your library
kbar.48:/nj/adm/src/openssh-3.2.3p1#

...and can't proceed past that.

My /usr/local area is common to all machines on my network so that
packages only have to be installed once and for everything else I've
ever ever installed it has worked beautifully, but I've hit this brick
wall now. I would hate to have to separate the /usr/local for the two
distributions, or to install from Solaris 8 over what is now working
for all Solaris 7 machines on my network since it will probably kill
it for all of them. Anyone have any idea of a flag I might be missing
of some other thing I might need to do?

Ernie



Relevant Pages

  • Re: OpenSSH Password Aging/Expiration on UW2.1.3
    ... Try using gcc compiler. ... >difficulties with UnixWare and not Solaris. ... >> Look at the thread 'OpenSSH and forced password change' ... >>> When user bob attempts to login, ...
    (comp.security.ssh)
  • Re: trojaned SSHD ?
    ... I'd recommend moving to OpenSSH, which supports both ssh1 and ssh2 ... platforms, including Solaris. ... Information relevant to the installation of SSH on NCMIR systems. ... * Install Zlib 1.1.2 libraries, compiling from source, on Solaris and IRIX ...
    (Focus-SUN)
  • Re: Solaris 10 smc problem
    ... "Jim" escribió en el mensaje ... How many processors does Solaris 10 for x86 support? ... Which is the better way to install a compiler? ...
    (comp.unix.solaris)
  • OpenSSH 3.2.3p1 incompatibilities between Solaris 7 and 8
    ... I get this on a Solaris 8 machine that has OpenSSH 3.2.3p1 installed ... checking for C compiler default output... ... or to install from Solaris 8 over what is now working ...
    (comp.security.ssh)
  • RE: Make problem Building 64 bit Perl 5.8.8 from source on Solaris 10 with gcc 3.4.6
    ... Solaris 10 with gcc 3.4.6 ... Make problem Building 64 bit Perl 5.8.8 from source on ... INSTALL notes and have looked through the hints script. ... compiler or make any changes to the system directories. ...
    (perl.dbi.users)