[465] in linux-security and linux-alert archive
Re: linux a.out ld.so problem
daemon@ATHENA.MIT.EDU (Jon Lewis)
Wed Nov 8 17:03:46 1995
Date: Tue, 7 Nov 1995 01:07:32 -0500 (EST)
From: Jon Lewis <jlewis@inorganic5.chem.ufl.edu>
To: medulla <medulla@infosoc.com>
cc: linux-security@tarsier.cv.nrao.edu
In-Reply-To: <Pine.LNX.3.91.951106061044.389A-100000@ereet.org>
On Mon, 6 Nov 1995, medulla wrote:
> something obvious? The ld.so man page clearly says the variable(s) are
> ignored when the app is suid or sgid, but this doesnt appear to be the case.
> hfpa:~# setenv LD_LIBRARY_PATH /tmp
> hfpa:~# strace -o ls.2 ./ls
> <snipped dir list>
> hfpa:~# grep /tmp ls.2
> uselib("/tmp/libc.so.4") = 0
I get the same thing and thought at first that it might be caused by you
doing all this as root...but its not. I get the same results...but I
think it may not be a problem. Even though I see the
'uselib("/tmp/libc.so.4") = 0' in the trace, I see none of the signs that
my hacked libc was actually used. It should have tried adding to
/etc/passwd and created a file in /tmp...but neither happened, and I know
this libc will work when used in the telnet hole.
------------------------------------------------------------------
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_____
