From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Andreas Herz <andi@geekosphere.org>, netfilter@vger.kernel.org
Subject: Re: [ANNOUNCE]: Release of nftables 0.099
Date: Tue, 21 Jan 2014 13:27:13 +0000 [thread overview]
Message-ID: <20140121132713.GA694@macbook.localnet> (raw)
In-Reply-To: <alpine.DEB.2.10.1401211401540.32183@blackhole.kfki.hu>
On Tue, Jan 21, 2014 at 02:12:23PM +0100, Jozsef Kadlecsik wrote:
> On Tue, 21 Jan 2014, Patrick McHardy wrote:
>
> > > > - use dynamic sized structures and add the timer at the end. Problem is that
> > > > we're in some cases already using optional members at the end, so it would
> > > > complicate the code a bit.
> > >
> > > I see that all three possibilities are far from perfect :/
> >
> > Well, all have some downsides, but I guess its something people will want
> > to have, otherwise Joszef wouldn't have added it, so we'll find a way.
>
> Sets with timeout give an easy way to stop/slow down scanners/attackers
> without the need (usually) of any maintenance when honeypots, detectors
> add the entries.
>
> ipset doesn't use struct timer_lists either, but implements
> timeout as a data extension (similar to conntrack). The elements are fixed
> sized, so it's simpler than the third case above for nftables.
Thanks, I'll have a closer look at this once I get to this.
prev parent reply other threads:[~2014-01-21 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 13:11 [ANNOUNCE]: Release of nftables 0.099 Patrick McHardy
2014-01-20 23:38 ` Release of nftables-plus 0.099 Jan Engelhardt
2014-01-20 23:41 ` [netfilter-core] " Patrick McHardy
2014-01-21 0:00 ` Jan Engelhardt
2014-01-21 0:26 ` Patrick McHardy
2014-01-21 11:59 ` [ANNOUNCE]: Release of nftables 0.099 Andreas Herz
2014-01-21 12:14 ` Patrick McHardy
2014-01-21 12:24 ` Andreas Herz
2014-01-21 12:32 ` Patrick McHardy
2014-01-21 12:43 ` Andreas Herz
2014-01-21 12:49 ` Patrick McHardy
2014-01-21 13:12 ` Jozsef Kadlecsik
2014-01-21 13:27 ` Patrick McHardy [this message]
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=20140121132713.GA694@macbook.localnet \
--to=kaber@trash.net \
--cc=andi@geekosphere.org \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter@vger.kernel.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