From owner-freebsd-security Tue Jun 20 15:37:53 2000 Delivered-To: freebsd-security@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 1FF2C37B5C5 for ; Tue, 20 Jun 2000 15:37:50 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from rac10.wam.umd.edu (root@rac10.wam.umd.edu [128.8.10.150]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id SAA18987 for ; Tue, 20 Jun 2000 18:37:44 -0400 (EDT) Received: from rac10.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac10.wam.umd.edu (8.9.3/8.9.3) with SMTP id SAA20296 for ; Tue, 20 Jun 2000 18:37:48 -0400 (EDT) Received: from rac10.wam.umd.edu (howardjp@localhost) by rac10.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA20291 for ; Tue, 20 Jun 2000 18:37:47 -0400 (EDT) Message-Id: <200006202237.SAA20291@rac10.wam.umd.edu> X-Authentication-Warning: rac10.wam.umd.edu: howardjp owned process doing -bs To: freebsd-security@freebsd.org Subject: Network ACLs Date: Tue, 20 Jun 2000 18:37:42 -0400 From: James Howard Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I know that the TrustedBSD group is working on filesystem ACLs. Will something similar be extended to the socket interface? Thanks, Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message