From owner-freebsd-security Thu Feb 6 03:22:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA03735 for security-outgoing; Thu, 6 Feb 1997 03:22:13 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA03694 for ; Thu, 6 Feb 1997 03:22:07 -0800 (PST) Received: by sovcom.kiae.su id AA02124 (5.65.kiae-1 ); Thu, 6 Feb 1997 14:13:58 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Thu, 6 Feb 97 14:13:57 +0300 Received: (from ache@localhost) by nagual.ru (8.8.5/8.8.5) id OAA03898; Thu, 6 Feb 1997 14:12:02 +0300 (MSK) Date: Thu, 6 Feb 1997 14:11:59 +0300 (MSK) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: Peter Wemm Cc: freebsd-security@freebsd.org Subject: Re: While we're on the subject... In-Reply-To: <855220778.617480@haywire.DIALix.COM> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 6 Feb 1997, Peter Wemm wrote: > I've been running with a version of it for what seems like 6 months now, but > my version was tied in with fixes to the P_SUGID flag rather than create > a new flag. As I already say in previous reply, I don't understand how it can be tied to P_SUGID flag. P_SUGID is set _after_ the code issue set*id() call and P_SUGIDEXEC is set immediately after suid binary launched even it not call set*id(). -- Andrey A. Chernov http://www.nagual.ru/~ache/