From owner-freebsd-hackers  Sat Sep  2 20:45:27 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id UAA29367
          for hackers-outgoing; Sat, 2 Sep 1995 20:45:27 -0700
Received: from vax.cs.pitt.edu (vax.cs.pitt.edu [136.142.79.5])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id UAA29347
          for <hackers@FreeBSD.ORG>; Sat, 2 Sep 1995 20:45:21 -0700
Received: from w2xo.pgh.pa.us by vax.cs.pitt.edu (8.6.10/1.14)
	id XAA06836; Sat, 2 Sep 1995 23:45:25 -0400
Received: (from durham@localhost) by w2xo.pgh.pa.us (8.6.11/8.6.9) id XAA00626; Sat, 2 Sep 1995 23:40:33 -0400
Date: Sat, 2 Sep 1995 23:40:31 -0400 (EDT)
From: Jim Durham <durham@w2xo.pgh.pa.us>
To: Terry Lambert <terry@lambert.org>
cc: hackers@FreeBSD.ORG
Subject: Re: A little strangness with 2.0.5
In-Reply-To: <199509022213.PAA02051@phaeton.artisoft.com>
Message-ID: <Pine.BSF.3.91.950902233257.589A-100000@w2xo.pgh.pa.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hackers-owner@FreeBSD.ORG
Precedence: bulk

On Sat, 2 Sep 1995, Terry Lambert wrote:

> > 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,
I should perhaps have phrased it better. I should have said..."seeing as
both the parent and child were SUID 'net' , why would changing the
GID matter?

I have to admit I don't know about exclusion groups. I'll have to do a little
reading on that.

Thanks,

-Jim Durham