From: "David Dabbs" <david@dabbs.net>
To: Hans Reiser <reiser@namesys.com>, George Beshers <gbeshers@comcast.net>
Cc: reiserfs-list@namesys.com
Subject: Re: viewprinting: what format should views be stored in?
Date: Sun, 22 Aug 2004 05:45:09 -0000 [thread overview]
Message-ID: <20040822054509.351BC15D06@mail03.powweb.com> (raw)
>
>The LSM paper cited (that does not require paying money) says very
>little about what they do with regards to the filesystem. Do you have a
>more informative URL?
>
Here's a concrete example of an LSM directory jail implementation. Not all the features I think you're aiming for but it is source and is indicative of what is possible (er, has already been done) with LSM.
David
http://lwn.net/Articles/57713/
From: "Serge E. Hallyn" <hallyn@CS.WM.EDU>
To: linux-security-module@wirex.com
Subject: dirjail module
Date: Mon, 10 Nov 2003 23:42:26 -0500
Attached are the header comments for a new LSM. I wrote it a few
months ago to address a particular need in a large-scale installation
for which DTE would have been inefficient. The module source can be
found at http://www.cs.wm.edu/~hallyn/dirjail.c.
I'll be curious to see if anyone else sees any use for this.
-serge
/*
* File: dirjail.c
*
* Description: Intended as an efficient prison for suspect child processes.
*
* Assume a large set of users. Each has a directory under, say,
* /home/sxx/username, where xx is a number from 00-03, and username
* is the account name. Their files may be served and processed by
* system processes and scripts (apache, accounting, etc). However,
* they may also, under /home/sxx/username, place their own scripts. You
* wish to confine the scripts to MOSTLY access only /home/sxx/username.
*
* modprobe dirjail
* for count in 00 01 02 03; do
* echo -n /home/s$count > /proc/jails
* done
* echo -n /bin > /proc/exec_exceptions
* echo -n /lib > /proc/exec_exceptions
* echo -n /tmp > /proc/rw_exceptions
* echo -n /proc > /proc/read_exceptions
*
* Now a script started from under /home/s01/user3 will be confined to
* only read, write, and execute files under /home/s01/user3. Exceptions
* to this are:
* it may execute anything under /bin
* it may read and write under /tmp
* it may read under /proc
*
* For the sake of simplicity, directory rx is always allowed.
* However, directory write and file rwx are restricted.
*
* Any children of said process will be convined to the same jail.
*
* Copyright (C) 2001 Serge E. Hallyn <hallyn@cs.wm.edu>
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
*/
next reply other threads:[~2004-08-22 5:45 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-22 5:45 David Dabbs [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-21 20:48 viewprinting: what format should views be stored in? David Dabbs
2004-08-21 7:38 David Dabbs
2004-08-21 8:59 ` Hans Reiser
2004-08-20 22:29 David Dabbs
2004-08-20 17:14 David Dabbs
2004-08-20 7:23 David Dabbs
2004-08-20 16:10 ` Valdis.Kletnieks
2004-08-20 21:04 ` George Beshers
2004-08-21 6:42 ` Hans Reiser
2004-08-19 7:40 David Dabbs
2004-08-19 11:21 ` David Greaves
2004-08-19 16:16 ` George Beshers
2004-08-20 6:19 ` Hans Reiser
2004-10-26 14:45 ` Lamont R. Peterson
2004-10-26 16:39 ` Hans Reiser
2004-10-26 16:57 ` George Beshers
2004-10-26 18:37 ` Hans Reiser
2004-10-26 20:20 ` George Beshers
2004-10-27 4:48 ` Hans Reiser
[not found] ` <4124D09A.1060208@comcast.net>
2004-08-19 17:31 ` David Greaves
2004-08-20 6:52 ` Hans Reiser
2004-08-20 12:08 ` George Beshers
2004-08-20 14:07 ` David Greaves
2004-10-26 15:54 ` Lamont R. Peterson
2004-10-27 1:04 ` David Masover
2004-08-20 6:13 ` Hans Reiser
2004-08-19 14:30 ` George Beshers
2004-08-18 7:52 David Dabbs
2004-08-18 18:37 ` David Masover
2004-08-18 21:47 ` George Beshers
2004-08-18 19:20 ` George Beshers
2004-08-18 20:20 ` Hans Reiser
2004-08-18 21:44 ` George Beshers
2004-08-18 21:48 ` Hans Reiser
2004-08-18 23:18 ` George Beshers
2004-08-19 0:42 ` Hans Reiser
2004-08-19 2:01 ` George Beshers
2004-08-19 5:50 ` Hans Reiser
2004-08-19 12:48 ` George Beshers
2004-08-20 6:59 ` Hans Reiser
2004-08-20 12:36 ` George Beshers
2004-08-20 18:14 ` Hans Reiser
2004-08-20 21:42 ` George Beshers
2004-08-18 19:34 ` Hans Reiser
2004-08-16 0:15 Hans Reiser
2004-08-16 1:48 ` George Beshers
2004-08-16 2:02 ` Hans Reiser
2004-08-16 13:47 ` George Beshers
2004-08-16 19:50 ` George Beshers
2004-08-17 7:07 ` Hans Reiser
2004-08-17 19:29 ` George Beshers
2004-08-17 20:28 ` Hans Reiser
2004-08-17 23:46 ` George Beshers
2004-08-18 2:22 ` Hans Reiser
[not found] ` <4121F4D6.8090506@comcast.net>
2004-08-17 19:43 ` Hans Reiser
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=20040822054509.351BC15D06@mail03.powweb.com \
--to=david@dabbs.net \
--cc=gbeshers@comcast.net \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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.