From: Roberto Nibali <ratz@tac.ch>
To: Diyab <diyab@diyab.net>
Cc: ratz@drugphish.ch, jonny@drugphish.ch,
SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: BSD Secure levels for linux
Date: Thu, 27 Nov 2003 20:45:49 +0100 [thread overview]
Message-ID: <3FC6546D.6020908@tac.ch> (raw)
In-Reply-To: <3FC54560.5050303@diyab.net>
Diyab wrote:
> Has anyone else run across the kernel patch that implements something
> similar to the BSD secure levels? Has anyone tried to use this with
> selinux? I'm also curious what the general thought of the idea is. Good
> idea? Bad idea? What do you think?
A fellow member (jonny) of drugphish.ch has done such an implementation, which
he called private[1]. It's based on LSM, has a user space control tool and a
pretty straightforward configuration file. You might want to have a look at it,
although it's far from being finished.
> Timothy,
>
> PS. You can find a short note from the author and the actual patch here:
> http://lwn.net/Articles/60096/ There is also a short article about it
> in the current weekly edition of LWN if you are a subscriber.
Hmm, interesting. We'll look into merging the remaining CAP_* functionalities
into the 'private' LSM module. Thanks for the pointer.
[1] http://www.drugphish.ch/~jonny/private.html
Best regards,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2003-11-27 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 0:29 BSD Secure levels for linux Diyab
2003-11-27 2:26 ` Russell Coker
2003-11-27 15:45 ` Diyab
2003-11-27 20:46 ` Tom
2003-11-27 22:32 ` Russell Coker
2003-11-27 19:45 ` Roberto Nibali [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=3FC6546D.6020908@tac.ch \
--to=ratz@tac.ch \
--cc=diyab@diyab.net \
--cc=jonny@drugphish.ch \
--cc=ratz@drugphish.ch \
--cc=selinux@tycho.nsa.gov \
/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.