netdev - Re: [Bugme-new] [Bug 13443] New: Scope 1 in multicast addresses in IPV6 should be node local

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] [day] [month] [year] [list]

Message-Id: <20090603.213723.03731994.davem@davemloft.net>
Date:	Wed, 03 Jun 2009 21:37:23 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	akpm@...ux-foundation.org
Cc:	netdev@...r.kernel.org, bugzilla-daemon@...zilla.kernel.org,
	bugme-daemon@...zilla.kernel.org, aviad.yehezkel5@...il.com
Subject: Re: [Bugme-new] [Bug 13443] New: Scope 1 in multicast addresses in
 IPV6 should be node local

From: Andrew Morton <akpm@...ux-foundation.org>
Date: Wed, 3 Jun 2009 14:40:31 -0700

>> I think scope 1 in multicast addresses in IPV6 should be node local (according
>> to all the documentation + rfc I found on the web) and therefore pkt's with
>> such destination address should not go on the wire.
>> When I try to send a udp pkt with sock_dgram to such ipv6 address with scope 1
>> I see the pkt is going on the wire and I can catch it on the other side by
>> joining this multicast address.

It looks like we need an addr_type and device check in ip6_output().

But in my opinion this is a pretty bogus requirement.  It's so easy
for things like netfilter, the packet scheduler classifier, or
other entities to get the packet to be rewritten from loopback
to an externally visible interface.
--
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