Date: Thu, 9 Nov 1995 10:19:02 -0600 (CST) From: Joe Greco <jgreco@brasil.moneng.mei.com> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: hackers@freebsd.org Subject: Re: Kerb Encr Telnet!! I found the problem! Message-ID: <199511091619.KAA22445@brasil.moneng.mei.com> In-Reply-To: <29977.815899604@time.cdrom.com> from "Jordan K. Hubbard" at Nov 8, 95 10:46:44 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > This was "painfully obvious" when I looked at it: > > > > anacreon# ls -l /usr/bin/telnet > > -r-xr-xr-x 1 bin bin 77824 Nov 4 18:52 /usr/bin/telnet > > anacreon# cd /usr/lib > > anacreon# ls -l libtel* > > -r--r--r-- 1 bin bin 39832 Nov 4 18:52 libtelnet.a > > -r--r--r-- 1 2035 wheel 9173 Jan 25 1995 libtelnet.so.2.0 > > -r--r--r-- 1 bin bin 43846 Nov 4 18:52 libtelnet_p.a > > But.. I don't understand how you have a `libtelnet.so.2.0' dated Jan > 25 on a fresh 2.1.0-950411-SNAP installation? > > Also, it makes no sense that telnet should die after loading the des > distribution - the des distribution *does not contain* telnet or > libtelnet! Check and see for yourself: > > jkh@freefall-> tar tvzf des.aa > drwxr-xr-x root/wheel 0 Nov 4 17:38 1995 ./ > drwxr-xr-x bin/bin 0 Nov 4 16:52 1995 bin/ > -r-xr-xr-x bin/bin 118784 Nov 4 16:52 1995 bin/ed > -r-xr-xr-x bin/bin 0 Nov 4 16:52 1995 bin/red link to bin/ed > drwxr-xr-x bin/bin 0 Nov 4 16:52 1995 sbin/ > -r-x------ bin/bin 147456 Nov 4 16:52 1995 sbin/init > drwxr-xr-x root/wheel 0 Nov 4 17:38 1995 usr/ > drwxr-xr-x bin/bin 0 Nov 4 16:52 1995 usr/bin/ > -r-xr-xr-x bin/bin 16384 Nov 4 16:52 1995 usr/bin/bdes > drwxr-xr-x bin/bin 0 Nov 4 16:52 1995 usr/lib/ > -r--r--r-- bin/bin 5456 Nov 4 16:52 1995 usr/lib/libcipher.a > -r--r--r-- bin/bin 9549 Nov 4 16:52 1995 usr/lib/libcipher.so.2.0 > -r--r--r-- bin/bin 6084 Nov 4 16:52 1995 usr/lib/libdescrypt.a > -r--r--r-- bin/bin 7258 Nov 4 16:52 1995 usr/lib/libdescrypt_p.a > -r--r--r-- bin/bin 13637 Nov 4 16:52 1995 usr/lib/libdescrypt.so.2.0 > lrwxr-xr-x bin/bin 0 Nov 4 16:52 1995 usr/lib/libcrypt.so.2.0 -> libdescrypt.so.2.0 > lrwxr-xr-x bin/bin 0 Nov 4 16:52 1995 usr/lib/libcrypt.a -> libdescrypt.a > lrwxr-xr-x bin/bin 0 Nov 4 16:52 1995 usr/lib/libcrypt_p.a -> libdescrypt_p.a > drwxr-xr-x bin/bin 0 Nov 4 17:38 1995 usr/share/ > drwxr-xr-x bin/bin 0 Nov 4 17:38 1995 usr/share/man/ > drwxr-xr-x bin/bin 0 Nov 4 16:52 1995 usr/share/man/man1/ > -r--r--r-- bin/bin 4413 Nov 4 16:52 1995 usr/share/man/man1/bdes.1.gz Hmm. Well that's all well and good except that I would expect that libtelnet would be in krb. Now, when I install systems, I _always_ wipe them squeaky clean, and so I have a hard time understanding where a Jan 25 dated binary would be coming from. Particularly since the several systems I checked were NOT upgraded, but total fresh installs on either new or low-level formatted disks.... Unless.... it's in the distribution. Dist Check. anacreon# cat krb* | gunzip | tar tvf - drwxr-xr-x root/wheel 0 Nov 4 19:38 1995 ./ .... -r--r--r-- bin/bin 39832 Nov 4 18:52 1995 usr/lib/libtelnet.a -r--r--r-- bin/bin 43846 Nov 4 18:52 1995 usr/lib/libtelnet_p.a -r--r--r-- bin/bin 46141 Nov 4 18:52 1995 usr/lib/libtelnet.so.2.0 -r--r--r-- bin/bin 22876 Nov 4 19:03 1995 usr/lib/libdes.a -r--r--r-- bin/bin 25842 Nov 4 19:03 1995 usr/lib/libdes_p.a -r--r--r-- bin/bin 27134 Nov 4 19:03 1995 usr/lib/libdes.so.2.0 .... That looks cool. Matter of fact, that looks great :-) anacreon# cat bin.* | gunzip | tar tvf - .... -r--r--r-- bin/bin 2292 Nov 4 18:37 1995 usr/lib/libtelnet.a -r--r--r-- bin/bin 8818 Nov 4 18:37 1995 usr/lib/libtelnet.so.2.0 .... Odd, that looks cool too. So where is this coming from? Oops. I think I know. anacreon# gunzip < compat20.tgz | tar tvf - .... -r--r--r-- jkh/wheel 9173 Jan 25 12:54 1995 usr/lib/libtelnet.so.2.0 .... And somebody installs this AFTER des and krb. So we have shared library collisions. From a quick re-examination of bin.*, it would appear that there is a mix of *.2.0, *.2.1, *.2.2, and *.3.0... is this good? Well at least it gives us a suggested workaround: don't install compat libraries. (That sucks but then I'm pretty religious about recompiling things, I just put in the compat stuff to ease transitions and make sure I can interoperate with other 2.0R systems, in my AMD-oriented environment - else things break). ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511091619.KAA22445>