From: Phil Sutter <phil@nwl.cc>
To: Reindl Harald <h.reindl@thelounge.net>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Arturo Borrero Gonzalez <arturo@netfilter.org>,
netfilter-devel@vger.kernel.org, kadlec@netfilter.org
Subject: Re: [iptables PATCH] iptables-nft: fix basechain policy configuration
Date: Fri, 9 Oct 2020 12:14:58 +0200 [thread overview]
Message-ID: <20201009101458.GG13016@orbyte.nwl.cc> (raw)
In-Reply-To: <0669e18b-661b-efec-fe15-e540290c3219@thelounge.net>
Hi Harald,
On Fri, Oct 09, 2020 at 12:07:57PM +0200, Reindl Harald wrote:
> Am 09.10.20 um 11:37 schrieb Phil Sutter:
> > I guess fundamentally this is due to legacy design which keeps builtin
> > chains in place at all times. We could copy that in iptables-nft, but I
> > like the current design where we just delete the whole table and start
> > from scratch.
> >
> > Florian made a related remark a while ago about flushing chains with
> > DROP policy: He claims it is almost always a mistake and we should reset
> > the policy to ACCEPT in order to avoid people from locking themselves
> > out. I second that idea, but am not sure if such a change is tolerable
> > at all.
> bad idea!
Why?
> nothing is locking you out just because of a short drop phase, at least
> not over the past 12 years, that's what tcp retransmits are for
What I had in mind was 'ssh somehost iptables -F INPUT'.
> when you once accept i have someone which should never have been
> accepted in the conntracking - sorry - but when i say drop i literally
> mean drop at any point in time
My English language parser failed this part, sorry. :)
Cheers, Phil
next prev parent reply other threads:[~2020-10-09 10:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 11:44 [iptables PATCH] iptables-nft: fix basechain policy configuration Arturo Borrero Gonzalez
2020-10-02 12:07 ` Phil Sutter
2020-10-02 12:15 ` Pablo Neira Ayuso
2020-10-02 12:28 ` Phil Sutter
2020-10-02 12:47 ` Pablo Neira Ayuso
2020-10-02 13:31 ` Phil Sutter
2020-10-02 14:39 ` Pablo Neira Ayuso
2020-10-08 17:31 ` Pablo Neira Ayuso
2020-10-09 8:29 ` Phil Sutter
2020-10-09 8:50 ` Pablo Neira Ayuso
2020-10-09 9:37 ` Phil Sutter
2020-10-09 10:07 ` Reindl Harald
2020-10-09 10:14 ` Phil Sutter [this message]
2020-10-09 10:28 ` Reindl Harald
2020-10-09 10:37 ` Jozsef Kadlecsik
2020-10-09 12:04 ` Phil Sutter
2020-10-09 19:05 ` Jozsef Kadlecsik
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=20201009101458.GG13016@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=arturo@netfilter.org \
--cc=h.reindl@thelounge.net \
--cc=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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;
as well as URLs for NNTP newsgroup(s).