netdev - Re: [PATCH v4 00/19] CALIPSO Implementation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20160623.152112.1146976941740701983.davem@davemloft.net>
Date:	Thu, 23 Jun 2016 15:21:12 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	huw@...eweavers.com
Cc:	netdev@...r.kernel.org, linux-security-module@...r.kernel.org,
	selinux@...ho.nsa.gov, pmoore@...hat.com
Subject: Re: [PATCH v4 00/19] CALIPSO Implementation

From: Huw Davies <huw@...eweavers.com>
Date: Tue, 21 Jun 2016 10:55:48 +0100

> On Tue, Jun 21, 2016 at 05:39:28AM -0400, David Miller wrote:
>> From: Huw Davies <huw@...eweavers.com>
>> Date: Mon, 20 Jun 2016 14:36:40 +0100
>> 
>> > This patch series implements RFC 5570 - Common Architecture Label IPv6
>> > Security Option (CALIPSO).  Its goal is to set MLS sensitivity labels
>> > on IPv6 packets using a hop-by-hop option.  CALIPSO is very similar to
>> > its IPv4 cousin CIPSO and much of this series is based on that code.
>> 
>> What tree do you expect to integrate this?
> 
> My understanding is that Paul Moore is happy to take them
> in via the SELinux tree.  However, these patches do touch
> some core networking code, such as the IPv6 option handling
> code (in a similar manner to the way CIPSO touched the IPv4
> option code), so if you have any comments on those aspects
> that would be good to hear.

No objections on my part.