From owner-freebsd-current Wed Nov 17 12:37:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B154E14CCB for ; Wed, 17 Nov 1999 12:37:31 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA90542 for ; Wed, 17 Nov 1999 12:37:27 -0800 (PST) Date: Wed, 17 Nov 1999 12:37:26 -0800 (PST) From: Julian Elischer To: freebsd-current@FreeBSD.ORG Subject: Re: PATCH for testing In-Reply-To: <199911172034.VAA04150@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG since the environment is supposed to be part of the address space it is ssupposed to be private.. On Wed, 17 Nov 1999, Oliver Fromme wrote: > Adam Wight wrote in list.freebsd-current: > > x I like the -e option when I'm root and trying to debug things. I > > x think that peter's fix seems to be ideal. You can find out about your > > x own uid, but no one else's unless you are root. > > > > I agree, but anything that runs suid has to be excluded as well. > > FWIW, I'd be against removing or restricting -e at all. > > Programs that put sensitive data into environment variables > (or expect the user to do that) are just _broken_. Removing > or restricting the -e option encourages such brokenness. > > Just my 0.02 Euro. > > Regards > Oliver > > -- > Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany > (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) > > "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" > (Terry Pratchett) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message