From owner-freebsd-hackers  Sat Sep  2 15:18:55 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id PAA09326
          for hackers-outgoing; Sat, 2 Sep 1995 15:18:55 -0700
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id PAA09313
          for <hackers@FreeBSD.ORG>; Sat, 2 Sep 1995 15:18:53 -0700
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA02051; Sat, 2 Sep 1995 15:13:44 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199509022213.PAA02051@phaeton.artisoft.com>
Subject: Re: A little strangness with 2.0.5
To: durham@w2xo.pgh.pa.us (Jim Durham)
Date: Sat, 2 Sep 1995 15:13:44 -0700 (MST)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.91.950902171150.346A@w2xo.pgh.pa.us> from "Jim Durham" at Sep 2, 95 05:35:14 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 482       
Sender: hackers-owner@FreeBSD.ORG
Precedence: bulk

> My problem is "solved" at the moment, but something is not "cricket"
> and may bite someone else. Why should the group ID have any effect
> on kill permissions?

A kill signal can be delivered to a process owned by your UID or a
process owned by your GID.  You seem to not be a memebr of the group
you SGID'ed to, so exclusion groups apply.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.