KTH krb4 and OpenSSL conflict building OpenSSH 3.0.2p1
Atro Tossavainen
atossava at cc.helsinki.fi
Sat Jan 19 01:33:49 EST 2002
Hi,
I configured OpenSSH 3.0.2p1 with
./configure --disable-suid-ssh --with-pam --with-kerberos4=/usr/athena \
--with-afs=/usr/afsws --with-ipaddr-display \
--with-ssl-dir=/afs/bi/v/@sys/libraries/openssl/latest
My "latest" OpenSSL is 0.9.6a. KTH krb4 is 1.1.
When linking the binaries, the KTH krb4 libdes conflicts with the
OpenSSL libdes. It seems to be possible to get around this like this:
where make emits
gcc -o ssh-keygen ssh-keygen.o -L. -Lopenbsd-compat/
-L/afs/bi/v/@sys/libraries/openssl/latest/lib -L/usr/athena/lib
-L/usr/afsws/lib -lssh -lopenbsd-compat -lkafs -lresolv -ldes -lkrb
-lpam -ldl -lutil -lz -lnsl -lcrypto -ldes
substitute
gcc -o ssh-keygen ssh-keygen.o -L. -Lopenbsd-compat/
-L/afs/bi/v/@sys/libraries/openssl/latest/lib -L/usr/athena/lib
-L/usr/afsws/lib -lssh -lopenbsd-compat -lkafs -lresolv -lkrb
-lpam -ldl -lutil -lz -lnsl -lcrypto
-L/afs/bi/v/@sys/libraries/openssl/latest/lib -ldes
instead. I don't know if the resulting binaries work, but at least it
gets around the conflict. Since OpenSSL is a requirement for OpenSSH,
I would imagine the people who implemented krb4 support would have
come across this already. Which obvious part am I missing?
--
Atro Tossavainen (Mr.) / The Institute of Biotechnology at
Systems Analyst, Techno-Amish & / the University of Helsinki, Finland,
+358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own.
< URL : http : / / www . iki . fi / atro . tossavainen / >
File attachments NOT welcome unless agreed to beforehand.
More information about the openssh-unix-dev
mailing list