All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Carter <jwcart2@tycho.nsa.gov>
To: Steve Lawrence <slawrence@tresys.com>
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: Re: Future of SETools and CIL
Date: Thu, 16 May 2013 10:46:26 -0400	[thread overview]
Message-ID: <5194F142.2080600@tycho.nsa.gov> (raw)
In-Reply-To: <5194E01F.2040505@tresys.com>

On 05/16/2013 09:33 AM, Steve Lawrence wrote:
> Another discussion we would like to have, which may affect the future of
> SETools/apol, is CIL. Is there still interest in CIL? And if so, have
> there been any thoughts on using and migrating to CIL? Is more work
> needed before this can happen? Has anyone put thought into higher level
> languages that could sit on top of CIL? If there is interest, this may
> affect the SETools changes, for example, syntactic policy analysis for
> CIL is likely very different than current policy.

I am still interested in CIL. In fact, I just got CIL to work on a 
translation of Refpolicy from early 2012. (And by work I mean produce a 
binary policy equivalent, according to sediff, with the binary produced 
by the Refpolicy build.) I just started this week on trying it against a 
recent version of Refpolicy. There are some issues that I need to work 
through; the biggest being how to handle the optional parameters to 
filetrans_pattern() and filetrans_add_pattern(). I hope to make both the 
CIL translation of Refpolicy and my many modifications to CIL available 
shortly.

I am also interested in resurrecting the earlier policy toolchain work 
to convert to the use of source modules and allow the use of CIL for 
policy builds.

-- 
James Carter <jwcart2@tycho.nsa.gov>
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:[~2013-05-16 14:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 13:33 Future of SETools and CIL Steve Lawrence
2013-05-16 14:10 ` Daniel J Walsh
2013-05-23 18:32   ` Steve Lawrence
2013-05-24 13:22     ` Daniel J Walsh
2013-05-16 14:46 ` James Carter [this message]
2013-05-23 18:43   ` Steve Lawrence
2013-05-23 19:43     ` James Carter
2013-05-23 20:24       ` Steve Lawrence
2013-05-16 16:37 ` Stephen Smalley
2013-05-23 18:28   ` Steve Lawrence
2013-05-17 12:42 ` Sven Vermeulen

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=5194F142.2080600@tycho.nsa.gov \
    --to=jwcart2@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=slawrence@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.