From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: Recovering .te and .fc files from modules
Date: Wed, 29 Nov 2006 16:33:27 -0500 [thread overview]
Message-ID: <456DFCA7.2090500@mentalrootkit.com> (raw)
In-Reply-To: <1164834319.23019.268.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Wed, 2006-11-29 at 15:38 -0500, Karl MacMillan wrote:
>> We've been getting requests for a tool to extract the .te and .fc files
>> from modules. Red Hat bugzilla for this at
>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=217761.
>>
>> I think this is a good idea and the dismod tool (located in
>> checkpolicy/test in the sources) is a good start at this. I'm mentioning
>> it here in case anyone has time or interest in creating this tool.
>
> You might want to separate the disassembling of a binary module to
> source policy from unpackaging a policy package, e.g. a
> semodule_unpackage utility could easily write out the individual
> components (binary module, file contexts, netfilter contexts), and then
> a nicer version of dismod could disassemble the binary module to textual
> representation.
>
Good point - added a note to the bugzilla.
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.
next prev parent reply other threads:[~2006-11-29 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 20:38 Recovering .te and .fc files from modules Karl MacMillan
2006-11-29 21:05 ` Stephen Smalley
2006-11-29 21:33 ` Karl MacMillan [this message]
2006-11-30 13:51 ` Stephen Smalley
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=456DFCA7.2090500@mentalrootkit.com \
--to=kmacmillan@mentalrootkit.com \
--cc=sds@tycho.nsa.gov \
--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.