Date: Mon, 23 Oct 1995 18:27:38 -0700 From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su> Cc: ache@freefall.freebsd.org, John Polstra <jdp@polstra.com>, freebsd-hackers@freebsd.org, gibbs@freefall.freebsd.org Subject: Re: ld.so, LD_NOSTD_PATH, and suid/sgid programs Message-ID: <199510240127.SAA21729@aslan.cdrom.com> In-Reply-To: Your message of "Tue, 24 Oct 1995 04:22:00 %2B0300." <Dau-3ZmiH1@ache.dialup.demos.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
>In message <m0t7Xo8-000078C@seattle.polstra.com> John Polstra writes: > >>> >Bogus argument in my opinion. The people who are going to use >>> >LD_NOSTD_PATH will know its effects. If you still want to argue >>> >about this, fine, but I'd like to put this issue to a vote. >>> >>> Yes, it can be used by intruder for hackers purposes, if he examine >>> previously what script does. > >>I don't think it can be used for hacking purposes. All it can possibly >>do is make a command fail to execute at all. Any shell script would >>have to be pretty silly to permit that to result in a security breach. > >Well, simple example: > > setuid_shared_binary > /tmp/file Fails since it cannot find its libraries so /tmp/file is empty > ... (f.e. few static commands) > setuid_static_binary < /tmp/file # OOPS! What? It can't handle empty input? > (umask is restrictive, of course) >-- >Andrey A. Chernov : And I rest so composedly, /Now, in my bed, >ache@astral.msk.su : That any beholder /Might fancy me dead - >http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. >RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510240127.SAA21729>