From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Moore Subject: Re: [RFC 3/7] NetLabel: CIPSOv4 engine Date: Fri, 23 Jun 2006 19:45:50 -0400 Message-ID: <449C7D2E.8000101@hp.com> References: <20060621200031.589235000@flek.zko.hp.com> <20060622.021223.125894633.davem@davemloft.net> <1151088481.2669.25.camel@localhost.localdomain> <20060623.131512.21593290.davem@davemloft.net> <1151094857.2669.51.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Ted , netdev@vger.kernel.org Return-path: Received: from atlrel9.hp.com ([156.153.255.214]:59625 "EHLO atlrel9.hp.com") by vger.kernel.org with ESMTP id S1752175AbWFWXpw (ORCPT ); Fri, 23 Jun 2006 19:45:52 -0400 To: James Morris In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org James Morris wrote: > > Support for interoperability with legacy CIPSO systems is something that I > think would be nice to have, if it can be done in a way which doesn't > impact deeply on core kernel code, and plays nicely with native Linux > infrastructure. > I'm not sure if you have had a chance to look at the new patch set yet but I know you have seen earlier versions and are at least familiar with the approach I am taking ... in your opinion is the NetLabel patch acceptable in its approach? -- paul moore linux security @ hp