netdev - Re: [PATCH net-next] net: ipv4: route: Fix sending IGMP messages with link 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] [day] [month] [year] [list]

Date:	Mon, 04 May 2015 00:04:22 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	andrew@...n.ch
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] net: ipv4: route: Fix sending IGMP messages
 with link address

From: Andrew Lunn <andrew@...n.ch>
Date: Fri,  1 May 2015 16:39:54 +0200

> In setups with a global scope address on an interface, and a lesser
> scope address on an interface sending IGMP reports, the reports can be
> sent using the other interfaces global scope address rather than the
> local interface address. RFC 2236 suggests:
> 
>      Ignore the Report if you cannot identify the source address of
>      the packet as belonging to a subnet assigned to the interface on
>      which the packet was received.
> 
> since such reports could be forged.
> 
> Look at the protocol when deciding if a RT_SCOPE_LINK address should
> be used for the packet.
> 
> Signed-off-by: Andrew Lunn <andrew@...n.ch>

Applied, thanks Andrew.
--
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