From owner-freebsd-security Thu Jul 2 00:08:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18702 for freebsd-security-outgoing; Thu, 2 Jul 1998 00:08:43 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18670 for ; Thu, 2 Jul 1998 00:08:30 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id DAA22222; Thu, 2 Jul 1998 03:06:50 -0400 (EDT) From: "Allen Smith" Message-Id: <9807020306.ZM22221@beatrice.rutgers.edu> Date: Thu, 2 Jul 1998 03:06:49 -0400 In-Reply-To: David Greenman "Re: bsd securelevel patch question" (Jul 1, 12:44am) References: <199807010744.AAA01700@implode.root.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: dg@root.com Subject: Re: bsd securelevel patch question Cc: security@FreeBSD.ORG, njs3@doc.ic.ac.uk, dima@best.net, abc@ralph.ml.org, tqbf@secnet.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Jul 1, 12:44am, David Greenman (possibly) wrote: > I'll resist any scheme that ties specific privileges to specific gids. To > me it seems too kludgy and I also suspect that most FreeBSD admins will be > quite unhappy about us hijacking a large block of gids for our special > purposes. Umm... OK, you're the boss. The block of gids I'd had in mind was above 65535, so I have my doubts how many people would be using those. Any ideas on alternate routes for port permission broadening? I haven't been able to look at Darren's version so far. -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message