From: Eric Leblond <eric@inl.fr>
To: netfilter@lists.netfilter.org
Subject: Re: providing partial access to iptables for non root user
Date: Wed, 23 Feb 2005 23:38:59 +0100 [thread overview]
Message-ID: <1109198339.17992.40.camel@porky> (raw)
In-Reply-To: <1108996157.5516.14.camel@hubcap.ljm.dom>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
On Mon, 2005-02-21 at 09:29 -0500, Jason Opperisano wrote:
> On Mon, 2005-02-21 at 06:33, Michael Jürgens wrote:
> > Hi,
> >
> > I´m looking for a solution to provide a non root user write access to a
> > chain.
> >
> > In this special case I have to provide the a mechanism to block some ip
> > adresses to connect to http.
> > But this should be done by a non root user. The non root user should not
> > change any other rule.
> >
> > Any ideas?
>
Why not to use a conf file with proper right ?
selected user could add rules in the script that will be automatically
inserted into the firewall via a cron task or a sudo script ?
BR,
--
Eric Leblond <eric@inl.fr>
INL
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-02-23 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 11:33 providing partial access to iptables for non root user Michael Jürgens
2005-02-21 13:38 ` Chris Brenton
2005-02-21 14:29 ` Jason Opperisano
2005-02-23 22:38 ` Eric Leblond [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=1109198339.17992.40.camel@porky \
--to=eric@inl.fr \
--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.