From owner-freebsd-security Wed Feb 7 17:50:31 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA21831 for security-outgoing; Wed, 7 Feb 1996 17:50:31 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA21797 for ; Wed, 7 Feb 1996 17:50:12 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA13788; Thu, 8 Feb 1996 12:17:53 +1030 From: Michael Smith Message-Id: <199602080147.MAA13788@genesis.atrad.adelaide.edu.au> Subject: Re: SS_PRIV, SIOCSIFADDR and rshd To: wollman@lcs.mit.edu (Garrett A. Wollman) Date: Thu, 8 Feb 1996 12:17:53 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, security@freebsd.org In-Reply-To: <9602071544.AA19509@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Feb 7, 96 10:44:17 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-security@freebsd.org Precedence: bulk Garrett A. Wollman stands accused of saying: > > > Anyone in a position to comment on this? I can't see anything obvious that > > resets SS_PRIV (or any of the socket state attributes) on either exec or > > set*id... > > Not a problem for the case of rshd. Our rshd always uses pipes to > talk to the inferior process. > > It's worth thinking about; I'll cons up a new setsockopt today to fix > the problem in the general case (at least for inetd). Hmm. There's no user struct visible at that level, so I guess it's not likely to be easy to check for uid == 0. > -GAWollman -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "wherever you go, there you are" - Buckaroo Banzai [[