From owner-freebsd-current Sat Feb 28 19:48:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02967 for freebsd-current-outgoing; Sat, 28 Feb 1998 19:48:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.31.78.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02930 for ; Sat, 28 Feb 1998 19:48:38 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id WAA23380; Sat, 28 Feb 1998 22:48:29 -0500 (EST) Date: Sat, 28 Feb 1998 22:48:29 -0500 (EST) From: "Matthew N. Dodd" To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Patches in support of security In-Reply-To: <199803010139.SAA02325@usr04.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 1 Mar 1998, Terry Lambert wrote: > Here are a set of patches that implement Juniper-like trusted > and untrusted interfaces (the default is untrusted). > > They incidently bump the interface flags from 16 to 32 buts (yea!): > > http://www.freebsd.org/~terry/DIFF.TRUST.txt > http://www.freebsd.org/~terry/DIFF.TRUST > http://www.freebsd.org/~terry/DIFF.ifconfig This looks useful. (or at least is a useful first step) While some policies may be enforced with creative firewall rules, these patches provide a clean interface at the application level. Is it possible to have them committed? /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message