netdev - Re: [Bugme-new] [Bug 28512] New: IPv6 SLAAC address preferred over static one as source address

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: <20110330073139.GA8190@boris.ghen.be>
Date:	Wed, 30 Mar 2011 09:31:39 +0200
From:	Geert Hendrickx <geert@...drickx.be>
To:	David Miller <davem@...emloft.net>
Cc:	akpm@...ux-foundation.org, netdev@...r.kernel.org,
	bugzilla-daemon@...zilla.kernel.org,
	bugme-daemon@...zilla.kernel.org
Subject: Re: [Bugme-new] [Bug 28512] New: IPv6 SLAAC address preferred over
 static one as source address

On Tue, Mar 29, 2011 at 17:20:00 -0700, David Miller wrote:
> This is debatable.
> 
> One could just as easily say that an address with a shorter preferred
> lifetime has been revalidated more recently, and therefore is more
> likely to be uptodate, valid, and lead to a usable path.


There we're at "most recent" again.  In practice, this will often be a SLAAC
address, which will rarely be preferred over a staticly configured one.



> I think the lack of specification for the final tie-breaker in the RFC
> was intentional :-)
> 
> The specification has to address this, and until the situation is more
> clear cut than it is now I don't see any benefit for changing Linux's
> behavior.  Especially since there is a configuration based workaround
> which works for people in the short-term.


What workaround are you referring to?


	Geert


-- 
geert.hendrickx.be :: geert@...drickx.be :: PGP: 0xC4BB9E9F
This e-mail was composed using 100% recycled spam messages!
--
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