netdev - Re: possible bug in IPv6 MLD retransmissions

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: <20130522172711.GC17240@obelix.rh>
Date:	Wed, 22 May 2013 14:27:11 -0300
From:	Flavio Leitner <fbl@...hat.com>
To:	David Stevens <dlstevens@...ibm.com>
Cc:	Hannes Frederic Sowa <hannes@...essinduktion.org>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	netdev-owner@...r.kernel.org,
	Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>
Subject: Re: possible bug in IPv6 MLD retransmissions

On Wed, May 22, 2013 at 07:30:39AM -0400, David Stevens wrote:
> First, I wouldn't call this a "bug"; it is listed as a "SHOULD", not a 
> "MUST",  so
> it is not required for compliance, though it is a good feature to add.
> 
> Second, I think doing this on all LL addresses unconditionally isn't a 
> good
> idea. If some configuration is using thousands of LL addrs for reasons of 
> their
> own, they would suddenly be blasted with unexpected MLD reports where
> they have none now. I don't see why tracking it would be such a problem --
> if nothing else, you could simply add a counter for the number of valid LL 
> addrs
> incremented on DAD completion, and send these whenever it transitions from 
> 0 to 1.

It becomes a bug (and that's why I started with 'possible') if dad
completes after the two MLD reports sent with ``::'' source, because
routers will ignore those initial reports and the system is left out.

Thanks,
-- 
fbl
--
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