[440] in linux-security and linux-alert archive
telnetd shared lib hole
daemon@ATHENA.MIT.EDU (Jon Lewis)
Sun Nov 5 16:21:35 1995
Date: Wed, 1 Nov 1995 15:53:26 -0500 (EST)
From: Jon Lewis <jlewis@inorganic5.chem.ufl.edu>
To: linux-security@tarsier.cv.nrao.edu
Call me silly, but since this hole operates by "secretly replacing your
real libc with Foldgers Crystals libc" and having telnetd use the bogus
libc, would all this be fixed with no need for careful patching /
environment cleaning if we simply compiled telnetd and statically linked
it? Then it would need no shared libs, and you'd be unable to force it to
load a hacked libc...no?
It may not be an elegant solution...but is it one at all?
------------------------------------------------------------------
Jon Lewis | Mime attachments are OK
jlewis@inorganic5.chem.ufl.edu | But please ask before sending
http://inorganic5.chem.ufl.edu | unsolicited huge files.
|
_____Finger jlewis@inorganic5.chem.ufl.edu for PGP public key_____
