From: Alistair Tonner <Alistair@nerdnet.ca>
To: netfilter@lists.netfilter.org
Subject: Re: Possible to block ports by user group?
Date: Mon, 5 Jul 2004 10:34:16 -0400 [thread overview]
Message-ID: <200407051034.16368.Alistair@nerdnet.ca> (raw)
In-Reply-To: <opsande9km4evsfm@smtp.pacific.net.th>
On July 5, 2004 12:29 am, Michael Frank wrote:
> On Sun, 04 Jul 2004 16:59:04 +0200, Cedric Blancher
<blancher@cartel-securite.fr> wrote:
> > Le dim 04/07/2004 à 15:16, Michael Frank a écrit :
> >> Would like to block ports depending on the group in use
> >
> > See owner match :
> >
> > cbr@anduril:~$ iptables -m owner --help
> > iptables v1.2.11
> > [...]
> > OWNER match v1.2.11 options:
> > [!] --uid-owner userid Match local uid
> > [!] --gid-owner groupid Match local gid
> > [!] --pid-owner processid Match local pid
> > [!] --sid-owner sessionid Match local sid
> > [!] --cmd-owner name Match local command name
> >
> > --gid-owner seems to satisfy your needs.
>
> Thank you for the pointer. This works very well.
>
> I think there is a problem though wrt ICMP requests. The following
> rule allows _everyone_ to ping, but I would expect only root to be able to.
>
> ACCEPT all -- anywhere anywhere OWNER UID match
> root
>
> This rule has no effect on ICMP i am mhf and can't ping.
>
> ACCEPT all -- anywhere anywhere OWNER UID match
> mhf
>
> This is with Vanilla kernel 2.4.24. Any know issue here?
>
I would suggest that in all likelyhood your ping/traceroute are setuid root.
*grin*
Alistair.
next prev parent reply other threads:[~2004-07-05 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 13:16 Possible to block ports by user group? Michael Frank
2004-07-04 14:06 ` Antony Stone
2004-07-05 4:17 ` Michael Frank
2004-07-04 14:59 ` Cedric Blancher
2004-07-05 4:29 ` Michael Frank
2004-07-05 14:34 ` Alistair Tonner [this message]
2004-07-05 16:35 ` Michael Frank
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=200407051034.16368.Alistair@nerdnet.ca \
--to=alistair@nerdnet.ca \
--cc=netfilter@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.