public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: Amon Ott <ao@rsbac.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: on-access events?
Date: Thu, 23 Dec 2004 17:16:26 -0500	[thread overview]
Message-ID: <41CB43BA.3050804@comcast.net> (raw)
In-Reply-To: <200412231016.25967.ao@rsbac.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm looking for a hint on which will possibly go into mainline kernel,
if any.  Right now there's supposedly a few things built on Dazuko, like
Clamuko (ClamAV on-access scanning); but I've yet to really encounter
anything aside from that that use Dazuko so :)

I'm thinking of a lot of things that can be done with on-access control
from userspace.

RSBAC and LSM seem to do almost the same thing, except that RSBAC
actually comes with a lot of modules to use it (LSM/SELinux are separate
projects, but both integrated into the kernel, AFAIK).  I don't see
RSBAC going into mainline; I don't know which is better though, LSM or
RSBAC.  This brings to mind pointless and random proof-of-concept tasks,
such as porting SELinux to RSBAC; or porting LSM to RSBAC (as an rsbac
module), or RSBAC to LSM (as an lsm module).

Amon Ott wrote:
| On Mittwoch, 22. Dezember 2004 19:49, John Richard Moser wrote:
|
|>What kinds of on-access event driving is there for Linux?  I'm
|
| looking
|
|>at Dazuko[1] right now, but not sure about what else is out there.
|
| I'm
|
|>sure I've seen several; is there anything in the kernel?
|
|
| Besides the LSM interface in 2.6 kernels there is also the RSBAC
| framework for 2.4 and 2.6, where you can register from kernel modules
| at runtime, http://www.rsbac.org.
|
| Dazuko plus caching has also been integrated as RSBAC module.
|
| Amon.

- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBy0O6hDd4aOud5P8RAt/eAJ9y8cGnbqggMLgT1pGQ3MsF3d/uagCgi/se
uwj+n448vDMislspw7CndQQ=
=ljdg
-----END PGP SIGNATURE-----

      reply	other threads:[~2004-12-23 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-22 18:49 on-access events? John Richard Moser
2004-12-23  9:16 ` Amon Ott
2004-12-23 22:16   ` John Richard Moser [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=41CB43BA.3050804@comcast.net \
    --to=nigelenki@comcast.net \
    --cc=ao@rsbac.org \
    --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