From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <456DFCA7.2090500@mentalrootkit.com> Date: Wed, 29 Nov 2006 16:33:27 -0500 From: Karl MacMillan MIME-Version: 1.0 To: Stephen Smalley CC: SELinux Mail List Subject: Re: Recovering .te and .fc files from modules References: <456DEFAD.6040706@mentalrootkit.com> <1164834319.23019.268.camel@moss-spartans.epoch.ncsc.mil> In-Reply-To: <1164834319.23019.268.camel@moss-spartans.epoch.ncsc.mil> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov 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.