All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken YANG <spng.yang@gmail.com>
To: SELinux List <selinux@tycho.nsa.gov>
Subject: which tool i should use for policy generation
Date: Thu, 12 Jul 2007 11:17:15 +0800	[thread overview]
Message-ID: <46959D3B.7040202@gmail.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GB18030, Size: 634 bytes --]



i find three papers about policy generation tools:

<<Guided Policy Generation for Application Authors>>
<<Madison: A New Approach to Policy Generation>>
<<Madison ¨C A New Approach to Policy Generation>>


it seems the last one is the last, so is that mean we
should use sepolgen rather than madison.

BTW, i notice the madison is not in fedora rawhide
repository, is this another reason we should use
sepolgen?


--
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.

             reply	other threads:[~2007-07-12  3:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12  3:17 Ken YANG [this message]
2007-07-12 12:09 ` which tool i should use for policy generation Stephen Smalley

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=46959D3B.7040202@gmail.com \
    --to=spng.yang@gmail.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.