From: bsniffen@mitre.org (Brian T. Sniffen)
To: Karl MacMillan <kmacmillan@mentalrootkit.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: MITRE releases Polgen 1.4
Date: Fri, 09 Feb 2007 16:31:23 -0500 [thread overview]
Message-ID: <m2k5yrrpas.fsf@dreaming.mitre.org> (raw)
In-Reply-To: <45CC87EE.9020407@mentalrootkit.com> (Karl MacMillan's message of "Fri\, 09 Feb 2007 09\:40\:46 -0500")
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
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.
-Brian
--
Brian T. Sniffen bsniffen@mitre.org
The MITRE Corporation 781-271-2904
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 1381 bytes --]
next prev parent reply other threads:[~2007-02-09 21:31 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 [this message]
2007-02-22 22:20 ` Karl MacMillan
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=m2k5yrrpas.fsf@dreaming.mitre.org \
--to=bsniffen@mitre.org \
--cc=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.