From owner-freebsd-current Mon Mar 24 07:27:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA13326 for current-outgoing; Mon, 24 Mar 1997 07:27:31 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA13218; Mon, 24 Mar 1997 07:25:50 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0w9BbH-00057u-00; Mon, 24 Mar 1997 08:23:55 -0700 To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= Subject: Re: issetuid() Cc: peter@freebsd.org, FreeBSD-current In-reply-to: Your message of "Mon, 24 Mar 1997 17:07:48 +0300." References: Date: Mon, 24 Mar 1997 08:23:55 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= writes: : Peter, as I remember you have plans to implement issetuid(). Right now too : many changes sneaked in the source tree which require it. As I think, : implementation can be done easily, just check P_SUGID bit. Also setuid() : etc syscalls must be cleaned slightly to not set this bit when not really : neccessary (i.e. when the same uid/gid is set). Do you have something for : review at this moment? There were already a bunch of other places that used the same code I did, or a variation on them. I at least tagged my with XXX should use issetugid(), others didn't. Warner