netdev - Re: [PATCH] ipv6: don't accept multicast traffic with scop 0

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20130211.145252.603354702530166412.davem@davemloft.net>
Date:	Mon, 11 Feb 2013 14:52:52 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	hannes@...essinduktion.org
Cc:	netdev@...r.kernel.org, yoshfuji@...ux-ipv6.org,
	erik.hugne@...csson.com
Subject: Re: [PATCH] ipv6: don't accept multicast traffic with scop 0

From: Hannes Frederic Sowa <hannes@...essinduktion.org>
Date: Mon, 11 Feb 2013 20:48:35 +0100

> On Sun, Feb 10, 2013 at 01:48:51PM +0100, Hannes Frederic Sowa wrote:
>> +	/*
>> +	 * RFC4291 2.7
>> +	 * Nodes must not originate a packet to a multicast address whose scop
>> +	 * field contains the reserved value 0; if such a packet is received, it
>> +	 * must be silently dropped.
> 
> Just nit-picking: The field is actually called scop without e, as pointed out
> by three erratas to RFC4291. :)

That's funny because I added the 'e' to your patches while applying
them, it just looks completely stupid to refer to this things as
'scop'.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html