From: "Rémi Denis-Courmont" <rdenis@simphalempin.com>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: Michael Stone <michael@laptop.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Security: Implement and document RLIMIT_NETWORK.
Date: Wed, 7 Jan 2009 18:52:27 +0200 [thread overview]
Message-ID: <200901071852.32078.rdenis@simphalempin.com> (raw)
In-Reply-To: <20090107114703.GB28161@ioremap.net>
Le mercredi 7 janvier 2009 13:47:03 Evgeniy Polyakov, vous avez écrit :
> The same goal can be achieved with 'owner' iptables match module btw.
Err no. iptables is _not_ suitable for userland applications dropping their
_own_ privileges. For privileged processes, it's clumsy at best, as iptables
does not quite work if more than one applications uses it. That's typically
your firewall configuration wizard or some custom admin-made script.
As for UNprivileged processes, iptables is not allowed.
As I understand it, Michael is trying to build something similar to SECCOMP,
only way less restrictive and way more usable by real-life userland programs.
--
Rémi Denis-Courmont
http://www.remlab.net/
next prev parent reply other threads:[~2009-01-07 16:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 5:48 RFC: Network privilege separation Michael Stone
2009-01-07 5:48 ` [PATCH] Security: Implement and document RLIMIT_NETWORK Michael Stone
2009-01-07 11:47 ` Evgeniy Polyakov
2009-01-07 16:52 ` Rémi Denis-Courmont [this message]
2009-01-07 17:48 ` Evgeniy Polyakov
2009-01-07 20:54 ` Rémi Denis-Courmont
2009-01-07 21:42 ` Evgeniy Polyakov
2009-01-07 18:35 ` C. Scott Ananian
2009-01-07 19:02 ` Evgeniy Polyakov
2009-01-07 19:39 ` Evgeniy Polyakov
2009-01-07 21:07 ` Michael Stone
2009-01-07 21:59 ` Evgeniy Polyakov
2009-01-08 0:56 ` Michael Stone
2009-01-08 4:27 ` Evgeniy Polyakov
2009-01-08 1:22 ` James Morris
2009-01-08 3:34 ` Michael Stone
2009-01-07 21:10 ` RFC: Network privilege separation Andi Kleen
2009-01-08 2:31 ` Michael Stone
2009-01-08 3:10 ` Andi Kleen
2009-01-08 4:51 ` Michael Stone
2009-01-08 5:41 ` Andi Kleen
2009-01-08 7:05 ` Oliver Hartkopp
2009-01-08 7:52 ` david
2009-01-08 10:43 ` Alan Cox
2009-01-12 18:44 ` Valdis.Kletnieks
2009-01-12 19:09 ` Bryan Donlan
2009-01-12 19:43 ` Andi Kleen
2009-01-12 19:47 ` Rémi Denis-Courmont
2009-01-12 20:14 ` Andi Kleen
2009-01-12 20:15 ` Rémi Denis-Courmont
2009-01-12 20:27 ` Evgeniy Polyakov
2009-01-12 20:39 ` Andi Kleen
2009-01-12 20:30 ` Rémi Denis-Courmont
2009-01-12 20:55 ` Andi Kleen
2009-01-12 20:47 ` Rémi Denis-Courmont
2009-01-12 21:50 ` Andi Kleen
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=200901071852.32078.rdenis@simphalempin.com \
--to=rdenis@simphalempin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@laptop.org \
--cc=netdev@vger.kernel.org \
--cc=zbr@ioremap.net \
/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).