All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Karl MacMillan <kmacmillan@mentalrootkit.com>, selinux@tycho.nsa.gov
Subject: Re: MITRE releases Polgen 1.4
Date: Thu, 22 Feb 2007 17:20:47 -0500	[thread overview]
Message-ID: <45DE173F.2020201@mentalrootkit.com> (raw)
In-Reply-To: <m2k5yrrpas.fsf@dreaming.mitre.org>

Brian T. Sniffen wrote:
> Karl MacMillan <kmacmillan@mentalrootkit.com> writes:
> 
>> Brian T. Sniffen wrote:
>>> Polgen handles the modularity of reference policy by searching through
>>> .if files to find interfaces that will handle access requirements of
>>> the program under analysis.  The technique used appears complementary
>>> to Karl MacMillan's Madison library.
>> Can you point me to the implementation inside of polgen? It would seem
>> to be nice to merge this functionality into a single upstream
>> implementation. Do you have any interest in pursuing this?
> 
> Absolutely.  The implementor, David Harris, is out on leave
> for the next few weeks.  I believe the analogous code is in
> polgen/src/patterns/{extract_ifs,refpol}.py.  We don't do everything
> Sepolgen does, but we do generate new types.  I'd love to see these
> capabilities merged.
> 

The easiest short term solution may be for you to use the generated 
information about interface vectors from sepolgen-ifgen. That is 
currently stored in /usr/share/sepolgen/interface_info, but will be 
moving to /var to support read-only /usr.

That file has information about each interface in the form of:

[InterfaceVector files_read_etc_files $1:source ]
$1,etc_t,lnk_file,read,getattr
$1,etc_t,file,read,lock,getattr,ioctl
$1,etc_t,dir,getattr,search,read,lock,ioctl

So a header - keyword, name, parameters (including whether it is used as 
a source, target, object class, or perm). The access vectors in the form 
of source_type,target_type,object_class,perms. You could feed this 
information straight into your current interface selection algorithm.

Alternatively, you can also use the interface selection algorithm. It 
already works pretty well (including using information flow information 
to select interfaces closer to the requested access). I'd welcome help 
making this better.

Karl

--
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-02-22 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21 15:51 selinux support on kernel 2.6.19.2 pt.2 Vincenzo Ciaglia
2007-02-08 23:48 ` MITRE releases Polgen 1.4 Brian T. Sniffen
2007-02-09 14:40   ` Karl MacMillan
2007-02-09 21:31     ` Brian T. Sniffen
2007-02-22 22:20       ` Karl MacMillan [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=45DE173F.2020201@mentalrootkit.com \
    --to=kmacmillan@mentalrootkit.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.