From owner-freebsd-security  Wed Feb  5 14:48:44 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA18956
          for security-outgoing; Wed, 5 Feb 1997 14:48:44 -0800 (PST)
Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA18949
          for <freebsd-security@FreeBSD.ORG>; Wed, 5 Feb 1997 14:48:39 -0800 (PST)
Message-Id: <199702052248.OAA18949@freefall.freebsd.org>
Received: by cheops.anu.edu.au
	(1.37.109.16/16.2) id AA203372883; Thu, 6 Feb 1997 09:48:03 +1100
From: Darren Reed <avalon@coombs.anu.edu.au>
Subject: Re: While we're on the subject...
To: tqbf@enteract.com
Date: Thu, 6 Feb 1997 09:48:03 +1100 (EDT)
Cc: freebsd-security@FreeBSD.ORG
In-Reply-To: <199702052042.OAA27560@enteract.com> from "Thomas H. Ptacek" at Feb 5, 97 02:42:07 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-security@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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 ?