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  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]
Date:	Sat, 11 Jan 2014 17:38:27 +0400
From:	Alexey Kuznetsov <>
To:	Fran├žois-Xavier Le Bail <>
	Hannes Frederic Sowa <>,
	"David S. Miller" <>,
	James Morris <>,
	Hideaki Yoshifuji <>,
	Patrick McHardy <>
Subject: Re: [PATCH net-next] IPv6: enable TCP to use an anycast address


On Sat, Jan 11, 2014 at 5:06 PM, Fran├žois-Xavier Le Bail
<> wrote:
> Many DNS root-servers use TCP with anycast (IPv4 and IPV6).
> see :
> "   L-Root service is provided using a single IPv4 address (
>    and a single IPv6 address (2001:500:3::42).  It should be noted that
>    it is preferable to refer to the service using its DNS name (L.ROOT-
>    SERVERS.NET) rather than literal addresses, since addresses can
>    change from time to time."

Is this all? It looks like this implies routing by deep packet inspection,
fetching some creepy node identification options from inside DNS payload
(not written directly, but  implied). This smells funky.

Actually, I was alerted by reset processing in your patch, it cannot be right.

Do not you think this must not be enabled for common use? At least
some separate sysctl disabled by default.
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists