From owner-freebsd-security  Sun Jun 14 18:41:37 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA14793
          for freebsd-security-outgoing; Sun, 14 Jun 1998 18:41:37 -0700 (PDT)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14762
          for <security@FreeBSD.ORG>; Sun, 14 Jun 1998 18:41:27 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA06234;
	Sun, 14 Jun 1998 18:38:47 -0700 (PDT)
Message-Id: <199806150138.SAA06234@implode.root.com>
To: njs3@doc.ic.ac.uk (Niall Smart)
cc: dima@best.net, security@FreeBSD.ORG, abc@ralph.ml.org
Subject: Re: bsd securelevel patch question 
In-reply-to: Your message of "Sun, 14 Jun 1998 22:19:29 BST."
             <E0ylKBV-0001IS-00@oak71.doc.ic.ac.uk> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sun, 14 Jun 1998 18:38:47 -0700
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> - implement a capabilities-based security model; even this isn't
>   fool-proof.

   As a former VMS developer, I've been wanting to do that for years in
FreeBSD. login.conf seems like the ideal place to build the privilege
list and the changes to the kernel aren't very difficult, just tedious.
One of these days...

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe security" in the body of the message