From: Andi Kleen <andi@firstfloor.org>
To: Michael Stone <michael@laptop.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: RFC: Network privilege separation.
Date: Wed, 07 Jan 2009 22:10:45 +0100 [thread overview]
Message-ID: <87mye2yg8a.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1231307334-9542-1-git-send-email-michael@laptop.org> (Michael Stone's message of "Wed, 7 Jan 2009 00:48:53 -0500")
Michael Stone <michael@laptop.org> writes:
> For the sake of discussion, I have written up and documented one possible
> implementation of this concept based on the idea of a new rlimit named
> RLIMIT_NETWORK in the following patch series.
>
> I eagerly await your questions, comments, suggestions, and improvements.
At least for outgoing packets you could already do it using the netfilter
owner match and a suitable uid. I suppose that could be also extended
for incoming packets.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2009-01-07 21:10 UTC|newest]
Thread overview: 39+ 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
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 ` Andi Kleen [this message]
2009-01-08 2:31 ` RFC: Network privilege separation 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
2009-01-13 8:06 ` Rémi Denis-Courmont
-- strict thread matches above, loose matches on Subject: below --
2009-01-08 12:08 Herbert Xu
2009-01-08 12:10 Herbert Xu
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=87mye2yg8a.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@laptop.org \
--cc=netdev@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