From owner-freebsd-current Wed Nov 17 12:34:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 8480B14CCB for ; Wed, 17 Nov 1999 12:34:18 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA04150 for freebsd-current@freebsd.org; Wed, 17 Nov 1999 21:34:18 +0100 (CET) (envelope-from olli) Date: Wed, 17 Nov 1999 21:34:18 +0100 (CET) From: Oliver Fromme Message-Id: <199911172034.VAA04150@dorifer.heim3.tu-clausthal.de> To: freebsd-current@freebsd.org Subject: Re: PATCH for testing Organization: Administration Heim 3 Reply-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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