From: antoine <antoine@nagafix.co.uk>
To: Colin Walters <walters@verbum.org>
Cc: "Christopher J. PeBenito" <cpebenito@tresys.com>,
SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: ANN: SELinux Reference Policy Release
Date: Thu, 16 Jun 2005 00:25:49 +0100 [thread overview]
Message-ID: <1118877949.10103.19.camel@localhost> (raw)
In-Reply-To: <1118874951.24338.35.camel@nexus.verbum.private>
(...)
Good work!
> # Define derived domains for GPG from @userdomain
> # @param user The user domain to derive from
> # @param userrole The user role to authorize for GPG
> function gpg_per_userdomain(domain user, role userrole) {
> derivedtype gpg_t from user
>
> domain_type(gpg_t)
> domain_entry_file(gpg_t, gpg_exec_t)
> role userrole types gpg_t
>
> ...
>
> The key idea here is that an IDE could actually parse this,
Not just IDEs, my brain finds it easier to parse too.
XML if overused nowadays.
> and easily
> determine programatically what types and roles are generated by the
> function, without doing hacks like expanding the M4 and parsing that,
> and then guessing.
Absolutely.
Antoine
--
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 prev parent reply other threads:[~2005-06-15 23:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 21:42 ANN: SELinux Reference Policy Release Christopher J. PeBenito
2005-06-15 22:35 ` Colin Walters
2005-06-15 23:25 ` antoine [this message]
2005-06-16 13:55 ` Christopher J. PeBenito
2005-06-16 17:46 ` Lorenzo Hernández García-Hierro
2005-06-21 23:25 ` antoine
2005-06-22 1:47 ` Karl MacMillan
2005-06-22 2:31 ` Lorenzo Hernández García-Hierro
2005-06-23 17:56 ` Karl MacMillan
2005-06-16 2:26 ` Karl MacMillan
2005-06-16 13:48 ` KaiGai Kohei
2005-06-16 15:17 ` Christopher J. PeBenito
2005-06-16 15:46 ` KaiGai Kohei
2005-06-16 15:47 ` Valdis.Kletnieks
2005-06-16 18:04 ` James Carter
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=1118877949.10103.19.camel@localhost \
--to=antoine@nagafix.co.uk \
--cc=cpebenito@tresys.com \
--cc=selinux@tycho.nsa.gov \
--cc=walters@verbum.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 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.