From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com,
johnwheffner@gmail.com, steffen.klassert@secunet.com,
fweimer@redhat.com
Subject: Re: [PATCH net-next v4 0/3] path mtu hardening patches
Date: Mon, 13 Jan 2014 11:25:04 -0800 (PST) [thread overview]
Message-ID: <20140113.112504.922587457597727366.davem@davemloft.net> (raw)
In-Reply-To: <1389258077-23282-1-git-send-email-hannes@stressinduktion.org>
From: hannes@stressinduktion.org
Date: Thu, 9 Jan 2014 10:01:14 +0100
> After a lot of back and forth I want to propose these changes regarding
> path mtu hardening and give an outline why I think this is the best way
> how to proceed:
I'm not going to fight this any more even though I still disagree with
these changes. John Heffner has not provided a coherent strong
argument for not doing this, in fact the counter arguments were
extremely vague.
I am pretty sure that now my worst fears will be realized and every
single distribution will not use the kernel's default, and everyone
will get this behavior rather than adminstrators making well informed
decisions about how to defend against these kind of situations when
enabling routing, or whether they'd even be exposed to the issue at
all in a particular setup.
Such is life.
next prev parent reply other threads:[~2014-01-13 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 9:01 [PATCH net-next v4 0/3] path mtu hardening patches hannes
2014-01-09 9:01 ` [PATCH net-next v4 1/3] ipv4: introduce ip_dst_mtu_maybe_forward and protect forwarding path against pmtu spoofing hannes
2014-01-09 9:01 ` [PATCH net-next v3 2/3] ipv6: introduce ip6_dst_mtu_forward and protect forwarding path with it hannes
2014-01-09 9:01 ` [PATCH net-next v2 3/3] ipv4: introduce hardened ip_no_pmtu_disc mode hannes
2014-01-13 19:25 ` David Miller [this message]
2014-01-13 19:35 ` [PATCH net-next v4 0/3] path mtu hardening patches John Heffner
2014-01-13 20:42 ` Hannes Frederic Sowa
2014-01-13 21:08 ` John Heffner
2014-01-13 21:28 ` Hannes Frederic Sowa
2014-01-13 21:50 ` John Heffner
2014-01-13 22:03 ` Hannes Frederic Sowa
2014-01-13 22:15 ` Hannes Frederic Sowa
2014-01-13 22:48 ` Florian Westphal
2014-01-13 23:18 ` Hannes Frederic Sowa
2014-01-13 22:12 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140113.112504.922587457597727366.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fweimer@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=johnwheffner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox