All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Mark Webb <elihusmails@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: policy development library documentation
Date: Wed, 06 May 2009 12:46:10 -0400	[thread overview]
Message-ID: <1241628370.27629.31.camel@localhost.localdomain> (raw)
In-Reply-To: <9f066ee90905060814m138c27a8g16d0e8b6a7b8fc00@mail.gmail.com>

On Wed, 2009-05-06 at 11:14 -0400, Mark Webb wrote:
> Greetings,
> 
> I am interested in writing a tool that will open and process a policy
> file.  I was looking around and was unable to determine the proper
> libraries to do this as most of the tools are written in python and
> the libs are written in C, so tracing is a little more difficult.  I
> would like to write this tool in C.
> 
> So my question is; where can I find documentation on the libraries
> that would do this work?  I have the source code for the setools
> project, and do not see much for documentation of the functions.

libsepol contains what you need to load a policy file and manipulate it.
It is unfortunately rather lacking in documentation.

libsepol was originally created by taking the core logic from
checkpolicy and moving it into a library so that it could be re-used by
other programs.  Since that time, a number of the policy analysis tools
have migrated to using libsepol as well, at least for processing the
binary policy.

-- 
Stephen Smalley
National Security Agency


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

      parent reply	other threads:[~2009-05-06 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06 15:14 policy development library documentation Mark Webb
2009-05-06 15:30 ` Daniel J Walsh
2009-05-06 16:46 ` Stephen Smalley [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=1241628370.27629.31.camel@localhost.localdomain \
    --to=sds@tycho.nsa.gov \
    --cc=elihusmails@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.