From: Dale Amon <amon@vnl.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Some minor thoughts on syntax/semantics
Date: Tue, 23 Sep 2003 16:09:27 +0100 [thread overview]
Message-ID: <20030923150926.GG21997@vnl.com> (raw)
There seems to be a bit of mental gymnastics involved
in reading allow statements. They are written like this:
allow this_t that_t:class {this that and the other};
but semantically we want to think of it as:
"Allow a domain this_t to do {this that and the other}
from something like that_t:class"
So I wonder if there was a reason you didn't go for
a similar syntax, eg
allow this_t {this that and the other} that_t:class;
Just curious.
--
------------------------------------------------------
IN MY NAME: Dale Amon, CEO/MD
No Mushroom clouds over Islandone Society
London and New York. www.islandone.org
------------------------------------------------------
--
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.
next reply other threads:[~2003-09-23 15:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 15:09 Dale Amon [this message]
2003-09-23 23:47 ` Some minor thoughts on syntax/semantics Brian May
2003-09-24 13:34 ` Russell Coker
2003-09-24 15:17 ` Dale Amon
2003-09-24 20:31 ` ssh policy hassles Dale Amon
2003-09-24 21:20 ` Kerry Thompson
2003-09-25 3:32 ` Russell Coker
2003-09-25 10:44 ` Dale Amon
2003-09-25 11:31 ` Dale Amon
2003-09-25 12:17 ` Dale Amon
2003-09-25 12:21 ` Russell Coker
2003-09-25 12:55 ` Stephen Smalley
2003-09-25 14:20 ` Dale Amon
2003-09-27 10:47 ` Dale Amon
[not found] ` <20030927133244.GC22582@vnl.com>
[not found] ` <20030927133352.GD22582@vnl.com>
2003-09-27 14:13 ` Russell Coker
2003-09-27 23:00 ` Dale Amon
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=20030923150926.GG21997@vnl.com \
--to=amon@vnl.com \
--cc=sds@epoch.ncsc.mil \
--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.