From: Lars Nooden <lars.curator@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Elmar Stellnberger <estellnb@gmail.com>,
netfilter@vger.kernel.org, peterb@chiark.greenend.org.uk,
chris@chrisbrenton.org
Subject: Re: block network access for certain users/groups
Date: Fri, 30 Jul 2010 14:34:44 +0300 [thread overview]
Message-ID: <4C52B8D4.30207@gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1007301036310.27811@obet.zrqbmnf.qr>
On 07/30/2010 12:00 PM, Jan Engelhardt wrote:
>
> Ref: http://marc.info/?l=netfilter&m=128043201731932&w=2
>
> On Thursday 2010-07-29 21:33, Lars Nooden wrote:
>> On 7/29/10 10:09 PM, Elmar Stellnberger wrote:
>>> iptables -A mychain -m owner --gid-owner blockedusergroup -j DROP
>>
>> For starters, consider using the REJECT target instead of DROP if for no other
>> reason than that it will make your engineering easier:
>>
>> http://www.chiark.greenend.org.uk/~peterb/network/drop-vs-reject
>
> That page - especially the summary - is leaving out one essential feature
> Gáspar already mentioned it in another thread; the CHAOS target from
> Xtables-addons.
CHAOS and TARPIT look about the same as DROP in regards to the question
of REJECT vs DROP. The same arguments apply about a quick response from
the filter or not.
http://www.chrisbrenton.org/2009/07/why-firewall-reject-rules-are-better-than-firewall-drop-rules/
http://www.chiark.greenend.org.uk/~peterb/network/drop-vs-reject
/Lars
next prev parent reply other threads:[~2010-07-30 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 19:09 block network access for certain users/groups Elmar Stellnberger
2010-07-29 19:33 ` Lars Nooden
2010-07-30 9:00 ` Jan Engelhardt
2010-07-30 11:34 ` Lars Nooden [this message]
2010-07-30 20:10 ` Elmar Stellnberger
2010-07-31 5:04 ` Richard Horton
-- strict thread matches above, loose matches on Subject: below --
2010-07-29 19:09 Elmar Stellnberger
2010-07-29 19:33 ` Richard Horton
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=4C52B8D4.30207@gmail.com \
--to=lars.curator@gmail.com \
--cc=chris@chrisbrenton.org \
--cc=estellnb@gmail.com \
--cc=jengelh@medozas.de \
--cc=netfilter@vger.kernel.org \
--cc=peterb@chiark.greenend.org.uk \
/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