From: Joshua Hudson <joshudson@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: BSD jail
Date: Fri, 12 Aug 2005 17:47:11 -0700 [thread overview]
Message-ID: <bda6d13a050812174768154ea5@mail.gmail.com> (raw)
I had been wanting this functionality myself, but for some reason it never found
its way into the stock kernel. I looked around, started coding,
looked some more,
coded some more, looked some more until I found this:
http://kerneltrap.org/node/3823
I suppose the reason it wasn't applied is lack of good IPv6 support.
It is perhaps about what I was looking for, but a slightly different method.
My idea was to cause no disturbance to the normal security chain, and
so maintain jails in the following manner (remember, the sys_jail call
is trusted)
1. Add an additional check to path_lookup (actually, a functioned
called by path_lookup)
to check for jail roots in addition to normal chroots.
2. Lockdown process visibility to only processes in the same jail.
3. Lockdown kill/ptrace/setpriority to processes in the same jail.
4. Lockdown capabilities to a restricted set that prevents novel
means of breaking the jail.
5. Restrict binding to one IPv4 and one IPv6 address (squash bind to
all to bind to that).
All of this is done in front of the normal security mechansim, so that
some non-default
security module will not accidentally break this.
I provided compatability for exactly the BSD jail(2) call, but did it
without breaking
programs that depend on chroot escapes working (there are a few).
I am currently about a third of the way to completion. This means that
I will finish
unless some other mechanism is provided before I do. I personally
don't care if my
patch is used (if released), but I want this functionality.
next reply other threads:[~2005-08-13 0:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 0:47 Joshua Hudson [this message]
2005-08-13 14:33 ` BSD jail Serge E. Hallyn
2005-08-13 16:33 ` Joshua Hudson
2005-08-14 11:56 ` Serge E. Hallyn
2005-08-14 21:34 ` Joshua Hudson
2005-08-14 23:25 ` Joshua Hudson
2005-08-16 1:35 ` Joshua Hudson
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=bda6d13a050812174768154ea5@mail.gmail.com \
--to=joshudson@gmail.com \
--cc=linux-kernel@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