The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lonnie Cumberland <lonnie@outstep.com>
To: linux-kernel@vger.kernel.org
Subject: Special Kernel Modification
Date: Sun, 04 Nov 2001 19:01:48 -0500	[thread overview]
Message-ID: <3BE5D6EC.8040204@outstep.com> (raw)

Hello All,

I am new to this list and am very interested in any help that you might 
be able to give me for a particular Linux project that I am working on.

I am currently using a Pentium III 500Mhz running Mandrake 8.0 Linux and 
Kernel 2.4.3 as a development system.

The basic problem that I am running into is that I am working on an 
Internet related project and thus need to ensure various types of 
document security for the eventual users of this system, if things go well.

I have look into using things like "chroot" to restrict the users for 
this very special server, but that solution is not what we need.

I am building a special xserver that will allow users to login and then 
the xserver will run a single application such as StarOffice. When the 
user exits from the application then the Xserver will log them out.

My problem is that I need to find a way to prevent the user from 
navigating out of their home directories.

I have also looking the possiblility of writing my own filesystem, but I 
am told that this needs to be done at the VFS level.

Is there someone who might be able to give me some information on how I 
could add a few lines to the VFS filesystem so that I might set some 
type of extended attribute to prevent users from navigating out of the 
locations.

Any help would be greatly appreciated,
Lonnie Cumberland


             reply	other threads:[~2001-11-05  0:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05  0:01 Lonnie Cumberland [this message]
2001-11-05  0:19 ` Special Kernel Modification Ryan Cumming
2001-11-05  0:29   ` lonnie
2001-11-05  1:04     ` Jan-Benedict Glaw
2001-11-05  3:04     ` Mike Fedyk
2001-11-06  0:34     ` Jorgen Cederlof
2001-11-06  0:38       ` lonnie
2001-11-05  0:22 ` Alan Cox
2001-11-05  0:39   ` Phil Sorber
2001-11-05  0:38 ` Rik van Riel
2001-11-05  1:04 ` Jeremy Jackson
2001-11-05  1:58 ` Jeff Dike
2001-11-05  2:14   ` Ryan Cumming
2001-11-05  4:02     ` Jeff Dike
2001-11-05  3:13       ` Ryan Cumming
2001-11-05  5:52         ` Jeff Dike
2001-11-05  5:30           ` Ryan Cumming
2001-11-05 14:22             ` Jeff Dike
2001-11-05 16:53           ` Andrea Arcangeli
2001-11-05 20:18             ` Jeff Dike
2001-11-05 19:05               ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2001-11-05  0:37 John Weber
     [not found] <E160aCK-0001Fs-00@localhost.suse.lists.linux.kernel>
     [not found] ` <200111050552.AAA06451@ccure.karaya.com.suse.lists.linux.kernel>
2001-11-05  6:22   ` 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=3BE5D6EC.8040204@outstep.com \
    --to=lonnie@outstep.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