All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: jail() system call (was Re: prevent breaking a chroot() jail?)
Date: Thu, 11 Jul 2002 16:56:36 -0700	[thread overview]
Message-ID: <20020711165636.B21285@figure1.int.wirex.com> (raw)
In-Reply-To: <1026428914.8085.11.camel@zaphod>; from spotter@cs.columbia.edu on Thu, Jul 11, 2002 at 07:08:13PM -0400

* Shaya Potter (spotter@cs.columbia.edu) wrote:
> Wow, this is what I need.  Would there be any interest in having this
> syscall in Linux, as I need to design something like this anyways for
> the research we are doing.
> 
> A first stab implementation would probably be as a module (as our
> research is based on a being usable just as a loadable module, w/o any
> direct kernel patch need, therefore until something is accepted into the
> kernel, we would need it like this), but we'd prefer it, and it
> definitely would be cleaner to have the jail tests integrated into the
> syscall and not wrapped by the module.

You could implement this policy in a security module.
http://lsm.immunix.org.

I don't believe you can do all of jail() with just capabilities, and as
a module it can always be extended.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

      reply	other threads:[~2002-07-11 23:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-05 15:16 prevent breaking a chroot() jail? Hank Leininger
2002-07-05 16:17 ` Ville Herva
2002-07-09 13:41   ` Bill Davidsen
2002-07-11 23:08   ` jail() system call (was Re: prevent breaking a chroot() jail?) Shaya Potter
2002-07-11 23:56     ` Chris Wright [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=20020711165636.B21285@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spotter@cs.columbia.edu \
    /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.