netdev - Re: [PATCH] ipv4/ipv6: check hop limit field on input

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: <20090602.023239.182993491.davem@davemloft.net>
Date:	Tue, 02 Jun 2009 02:32:39 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	john.dykstra1@...il.com
Cc:	brian.haley@...com, dada1@...mosbay.com, nicolas.dichtel@...nd.com,
	fw@...len.de, netdev@...r.kernel.org
Subject: Re: [PATCH] ipv4/ipv6: check hop limit field on input

From: John Dykstra <john.dykstra1@...il.com>
Date: Tue, 02 Jun 2009 09:22:10 +0000

> On Mon, 2009-06-01 at 19:02 -0700, David Miller wrote:
>> And I even remember there are applications that use multicast and
>> a hop limit of zero explicitly to keep application traffic only on
>> the local subnet.  So any change like that proposed could break
>> things.
> 
> Are you thinking of multicast apps that explicitly set a hop limit, or Multicast
> Listener Discovery?  The hop limit specified for MLDv2 messages is one,
> not zero.

I am very much thinking of multicast apps that explicitly set a hop
limit.

The proof is in the pudding.  As mentioned in other parts of this
thread, we explicitly DO NOT allow a zero normal socket TTL option
but we DO allow a zero multicast TTL socket option to be set.
--
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