netdev - Re: [PATCH net-next] ipv4: introduce hardened ip_no_pmtu

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]

Date:	Tue, 31 Dec 2013 00:37:11 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	hannes@...essinduktion.org
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] ipv4: introduce hardened ip_no_pmtu_disc mode

From: Hannes Frederic Sowa <hannes@...essinduktion.org>
Date: Sat, 21 Dec 2013 01:10:54 +0100

> This new ip_no_pmtu_disc mode only allowes fragmentation-needed errors
> to be honored by protocols which do more stringent validation on the
> ICMP's packet payload. This knob is useful for people who e.g. want to
> run an unmodified DNS server in a namespace where they need to use pmtu
> for TCP connections (as they are used for zone transfers or fallback
> for requests) but don't want to use possibly spoofed UDP pmtu information.
> 
> Currently the whitelisted protocols are TCP, SCTP and DCCP as they check
> if the returned packet is in the window or if the association is valid.
> 
> Signed-off-by: Hannes Frederic Sowa <hannes@...essinduktion.org>

I think this is going to have the same problem as the forwarding
sysctl, someone is going to convince some distribution to turn this
thing to the new "3" hardened mode by default.

I'm not applying this... for now, sorry.
--
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