From owner-freebsd-security  Wed Feb  5 14:11:55 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA16071
          for security-outgoing; Wed, 5 Feb 1997 14:11:55 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA16064
          for <freebsd-security@FreeBSD.ORG>; Wed, 5 Feb 1997 14:11:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id OAA11478; Wed, 5 Feb 1997 14:11:36 -0800 (PST)
Message-Id: <199702052211.OAA11478@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: tqbf@enteract.com
cc: freebsd-security@FreeBSD.ORG
Subject: Re: While we're on the subject... 
In-reply-to: Your message of "Wed, 05 Feb 1997 14:42:07 CST."
             <199702052042.OAA27560@enteract.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 05 Feb 1997 14:11:36 -0800
Sender: owner-security@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>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()? 

   It might not be a sufficient interface to solve the problem, but it is
being considered and will likely be implemented once we get beyond this
current mess.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project