netdev - Re: [net-next fragmentation icmp v5 0/3] fragmentation ICMP

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: <20150517.234833.1850042378148567219.davem@davemloft.net>
Date:	Sun, 17 May 2015 23:48:33 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	azhou@...ira.com
Cc:	netdev@...r.kernel.org
Subject: Re: [net-next fragmentation icmp v5 0/3] fragmentation ICMP

From: Andy Zhou <azhou@...ira.com>
Date: Fri, 15 May 2015 14:15:34 -0700

> Currently, we send ICMP packets when errors occur during fragmentation or
> de-fragmentation.  However, it is a bug when sending those ICMP packets
> in the context of using netfilter for bridging.
> 
> Those ICMP packets are only expected in the context of routing, not in
> bridging mode.
> 
> The local stack is not involved in bridging forward decisions, thus
> should be not used for deciding the reverse path for those ICMP messages.
> 
> This bug only affects IPV4, not in IPv6.

Series applied, thanks Andy.
--
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