From owner-freebsd-security  Thu Feb  6 01:20:16 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA24945
          for security-outgoing; Thu, 6 Feb 1997 01:20:16 -0800 (PST)
Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA24853
          for <freebsd-security@freebsd.org>; Thu, 6 Feb 1997 01:20:00 -0800 (PST)
Received: (from news@localhost) by haywire.DIALix.COM (8.8.4/8.8.2) id RAA21094 for freebsd-security@freebsd.org; Thu, 6 Feb 1997 17:19:39 +0800 (WST)
X-Authentication-Warning: haywire.DIALix.COM: news set sender to usenet-request@haywire.dialix.com using -f
Received: from GATEWAY by haywire.DIALix.COM with netnews
	for freebsd-security@freebsd.org (problems to: usenet@haywire.dialix.com)
To: freebsd-security@freebsd.org
Date: 6 Feb 1997 09:19:38 GMT
From: peter@spinner.DIALix.COM (Peter Wemm)
Message-ID: <855220778.617480@haywire.DIALix.COM>
Organization: DIALix Internet Services
References: <199702052042.OAA27560@enteract.com>
Subject: Re: While we're on the subject...
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <199702052248.OAA18949@freefall.freebsd.org>,
	avalon@coombs.anu.edu.au (Darren Reed) writes:
> In some mail from Thomas H. Ptacek, sie said:
>> 
>> OpenBSD has the locale issue resolved reliably already.
>> 
>> OpenBSD supports issetugid().
>> 
>> Thus, I can tell, even when I'm deep in libc, if I was called from an SUID
>> program. I can do that because execve() flipped a bit in my proc structure
>> when it noticed that I was SUID.
>> 
>> This is a good thing. 
>> 
>> Meaningless UID checks probably aren't. Anything could have happened to my
>> creds, depending on the programmer calling the library, and I have no way
>> of determining what happened. 
>> 
>> What's holding FreeBSD up on supporting issetugid()? 
> 
> Has anyone done a send-pr to send it to freebsd ?

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.

-Peter