From: ramsdell@mitre.org (John D. Ramsdell)
To: "Karl MacMillan" <kmacmillan@tresys.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Fedora Core 2 setools RPM
Date: 18 Jun 2004 09:00:33 -0400 [thread overview]
Message-ID: <ogtpt7x10ni.fsf@mitre.org> (raw)
In-Reply-To: <200406171847.i5HIlPSf000906@gotham.columbia.tresys.com>
"Karl MacMillan" <kmacmillan@tresys.com> writes:
> ... We will be putting an interim release out soon and will include
> the installation of the include files and libraries (shared and
> static).
Great news. I would greatly appreciate it if the libapol API includes
access to CONSTRAIN statements in a policy file. I strongly suspect
the API could then be used to provide slat all the information it
needs to analyze a policy.
I also noticed that it appears that none of the setools documentation
tells users that your flow analysis ignores CONSTRAIN statements in a
policy. I think users should know this fact.
$ grep -i constrain */*.in
docs-src/apol_help_text.in: You can use any regular expression to constrain the search. So
$
--
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:[~2004-06-18 13:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 21:07 Fedora Core 2 policy source Kratzer, James R.
2004-06-15 23:26 ` Fedora Core 2 setools RPM John D. Ramsdell
2004-06-16 13:37 ` Stephen Smalley
2004-06-16 16:58 ` Daniel J Walsh
2004-06-17 9:47 ` SE Linux enhanced strace for Fedora Core 2 John D. Ramsdell
2004-06-17 15:36 ` Fedora Core 2 setools RPM Karl MacMillan
2004-06-17 15:58 ` Stephen Smalley
2004-06-17 18:47 ` Karl MacMillan
2004-06-18 13:00 ` John D. Ramsdell [this message]
2004-06-18 14:13 ` Stephen Smalley
2004-06-18 17:26 ` Joshua D. Guttman
2004-06-18 17:51 ` Stephen Smalley
2004-06-18 18:18 ` Joshua D. Guttman
2004-06-18 18:43 ` Stephen Smalley
2004-06-18 19:31 ` Joshua D. Guttman
2004-06-18 20:09 ` Stephen Smalley
2004-06-21 13:16 ` Frank Mayer
2004-06-21 13:14 ` Frank Mayer
2004-06-21 13:43 ` Joshua D. Guttman
2004-06-21 15:26 ` Frank Mayer
2004-06-21 15:28 ` Frank Mayer
2004-06-19 5:33 ` Russell Coker
2004-06-19 13:09 ` Serge E. Hallyn
2004-06-18 13:09 ` John D. Ramsdell
2004-06-21 13:04 ` Frank Mayer
2004-06-21 15:43 ` John D. Ramsdell
2004-06-17 18:31 ` John D. Ramsdell
2004-06-15 23:33 ` Fedora Core 2 policy source John D. Ramsdell
2004-06-16 1:25 ` John D. Ramsdell
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=ogtpt7x10ni.fsf@mitre.org \
--to=ramsdell@mitre.org \
--cc=kmacmillan@tresys.com \
--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.