mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Valdis.Kletnieks@vt.edu,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: serue@us.ibm.com, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: TOMOYO Linux Security Goal
Date: Mon, 31 Dec 2007 07:27:51 -0800 (PST)	[thread overview]
Message-ID: <728764.75184.qm@web36608.mail.mud.yahoo.com> (raw)
In-Reply-To: <7781.1198996100@turing-police.cc.vt.edu>


--- Valdis.Kletnieks@vt.edu wrote:
 
> I'm pretty sure that most of the security community agrees on what "correct"
> means - the disagreement is in the most cost-effective way to *create* one.

Struth. (I'm practicing my Australian, it's gotten rusty)
I say that the the only rational way to create a policy is to
decide what you want the system to do and create your policy
based on that. I think that calling something that does nothing
more than enforce existing behavior without thought on what the
behavior ought to be a "policy" does disservice to the entire
security community. I realize that I'm in the minority on this
one. Oh well.


Casey Schaufler
casey@schaufler-ca.com

      reply	other threads:[~2007-12-31 15:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-25 12:33 Tetsuo Handa
2007-12-26 16:42 ` Serge E. Hallyn
2007-12-27 13:00   ` Tetsuo Handa
2007-12-27 14:54     ` Serge E. Hallyn
2007-12-28 14:32       ` Tetsuo Handa
2007-12-28 15:12         ` Serge E. Hallyn
2007-12-29  3:43           ` Tetsuo Handa
2007-12-31 15:17             ` Serge E. Hallyn
2007-12-31 15:25               ` Tetsuo Handa
2007-12-31 16:17                 ` Serge E. Hallyn
2007-12-28 17:23         ` Valdis.Kletnieks
2007-12-30  0:02           ` Pavel Machek
2007-12-30  5:29           ` Tetsuo Handa
2007-12-30  6:28             ` Valdis.Kletnieks
2007-12-31 15:27               ` Casey Schaufler [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=728764.75184.qm@web36608.mail.mud.yahoo.com \
    --to=casey@schaufler-ca.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=serue@us.ibm.com \
    /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

all inboxes | Powered by JetHome®