From: Casey Schaufler <casey@schaufler-ca.com>
To: "Lorenzo \"Hernández\" \"García-Hierro\"" <lorenzo@gnu.org>,
Valdis.Kletnieks@vt.edu
Cc: rsbac@rsbac.org,
"linux-security-module@wirex.com"
<linux-security-module@wirex.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Thoughts on the "No Linux Security Modules framework" old claims
Date: Wed, 16 Feb 2005 08:07:10 -0800 (PST) [thread overview]
Message-ID: <20050216160710.23689.qmail@web50201.mail.yahoo.com> (raw)
In-Reply-To: <1108560543.3826.89.camel@localhost.localdomain>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1646 bytes --]
--- Lorenzo Hernández García-Hierro <lorenzo@gnu.org>
wrote:
> ... but think it's main
> shortcoming is that it cuts
> performance
Ya'know, I keep hearing this assertion, but
the evidence of actual system implementations
that have been measured to determine this
"performance impact" is that there is no
difference except in contrived cases. In
contrived cases the performance is better
if you do the "special" checks first.
> and adds further overlapping to the DAC
> checks, that should
> be the first ones being called (as most times they
> do) and then apply
> the LSM basis, so, post-processing will be only
> required if the DAC
> checks get in override or passed, without adding
> too-much overhead to
> the current behavior.
No. There are a number of reasons, including
audit and nearline storage issues that make it
important to do the special checks first. Some
access control schemes may not work if the
Classic DAC check is done first.
> So, I just agree partially, but yes, maybe modifying
> the DAC checks
> themselves and add what-ever-else helper function to
> handle by-default
> auditing in certain operations could be interesting.
I remain a advocate of authoritative hooks.
> I think it could be worthy to have a roadmap in a
> wiki or even talk
> about a one, trying to write it, so, we all could
> know what needs to be
> improved and done, getting a higher percentage of
> mainline-accepted
> approaches.
Sigh.
=====
Casey Schaufler
casey@schaufler-ca.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2005-02-16 16:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 22:38 Thoughts on the "No Linux Security Modules framework" old claims Lorenzo Hernández García-Hierro
2005-02-16 4:21 ` Valdis.Kletnieks
2005-02-16 13:29 ` Lorenzo Hernández García-Hierro
2005-02-16 13:30 ` Stephen Smalley
2005-02-16 16:07 ` Casey Schaufler [this message]
2005-02-16 15:52 ` Casey Schaufler
2005-02-16 17:41 ` Valdis.Kletnieks
2005-02-21 10:19 ` [rsbac] " Amon Ott
2005-02-21 17:15 ` Lorenzo Hernández García-Hierro
2005-02-21 17:50 ` Casey Schaufler
2005-02-22 8:57 ` Amon Ott
2005-02-22 15:23 ` Casey Schaufler
2005-02-24 0:55 ` Kurt Garloff
2005-02-24 8:28 ` Amon Ott
2005-02-25 10:14 ` Kurt Garloff
2005-02-23 21:37 ` Crispin Cowan
2005-02-23 22:00 ` Lorenzo Hernández García-Hierro
2005-02-23 22:07 ` Crispin Cowan
2005-02-23 22:34 ` Lorenzo Hernández García-Hierro
2005-02-24 13:23 ` Stephen Smalley
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=20050216160710.23689.qmail@web50201.mail.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=lorenzo@gnu.org \
--cc=rsbac@rsbac.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