From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] interface typos
Date: Wed, 12 Jan 2011 15:09:24 -0500 [thread overview]
Message-ID: <4D2E0A74.2070900@tresys.com> (raw)
In-Reply-To: <201101091146.43353.russell@coker.com.au>
On 1/8/2011 7:46 PM, Russell Coker wrote:
> Could you please add to the feature-list for the policy compilation tools a
> feature to refuse an interface which requires a type that isn't defined in the
> matching .te file?
>
> I just wasted an hour because of a typo in an interface. :(
With CIL, refpolicy will become a proper language with a proper
compiler. So syntax errors like typos will be caught.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2011-01-12 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 0:46 [refpolicy] interface typos Russell Coker
2011-01-12 20:09 ` Christopher J. PeBenito [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=4D2E0A74.2070900@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.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 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.