All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Sanjai Narain <narain@research.telcordia.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: SELinux policy parser
Date: Thu, 30 Oct 2008 15:37:50 -0400	[thread overview]
Message-ID: <490A0D0E.9060703@redhat.com> (raw)
In-Reply-To: <490A0775.8040001@research.telcordia.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sanjai Narain wrote:
> Hello, I would appreciate pointers to any tools that parse SELinux
> policy files (either text or binary). I am planning to write algorithms
> to analyze such policies.
> 
> Not sure if this makes sense but given that tools like apol  read policy
> files, can they be made to dump their internal representations into a
> text file?
> 
> Thanks. -- Sanjai
> 
> 
> -- 
> 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.
Take a look at sesearch.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkkKDQ4ACgkQrlYvE4MpobMpoQCgghWWdI9ztFNO005ss4sTuCZe
RwgAn1T8zw3JruIIrQQzBmrhM0vXyMhY
=qTG8
-----END PGP SIGNATURE-----

--
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:[~2008-10-30 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 19:13 SELinux policy parser Sanjai Narain
2008-10-30 19:37 ` Daniel J Walsh [this message]
2008-10-30 20:18   ` Sanjai Narain

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=490A0D0E.9060703@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=narain@research.telcordia.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.