mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Ruder <aeruder@ksu.edu>
To: linux-kernel@vger.kernel.org
Subject: ANN: Trustees linux for the 2.6 kernel
Date: Sun, 14 Nov 2004 15:54:01 -0600	[thread overview]
Message-ID: <4197D3F9.2080008@ksu.edu> (raw)

Hello all,

I have ported Vyacheslav Zavadsky's work with trustees 
(http://trustees.sourceforge.net) to the Linux security module API.

Trustees is an advanced Linux permission system inspired by Netware. It 
allows a system administrator to attach "trustees" to any directory or 
file. All subdirectories and files in that directory will also inherit 
these trustees. Trustee rights can be overridden, denied or added to in 
subsequent directories.

In short, it is a recursive directory-based replacement for POSIX acls. 
   All permissions are managed from a central file and thus allows even 
filesystems (network, vfat, etc.) without extended attribute support to 
have an advanced permission scheme. It should compile against any 
version of the 2.6 kernel with CONFIG_SECURITY enabled (it currently 
compiles as just an external module).

Please see my website for more information:
    http://www.aeruder.net/trustees/

Download:
    http://www.aeruder.net/trustees/download.php?download=current

Documentation:
    http://www.aeruder.net/trustees/documentation.php?download=current

I have been using it for a couple weeks with no problems, but your 
mileage may vary.  The code still needs some cleanups, and I need to 
figure out how to do some benchmarking on the performance hit, but I 
would very much so appreciate feedback, bug-reports, etc.

Thanks and I am not on the list so please Cc any replies,
Andrew Ruder

                 reply	other threads:[~2004-11-14 21:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4197D3F9.2080008@ksu.edu \
    --to=aeruder@ksu.edu \
    --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

Powered by JetHome