From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Jason <jason@fatpipeinc.com>
Subject: Re: audit without python?
Date: Tue, 25 Oct 2011 14:09:43 -0400 [thread overview]
Message-ID: <201110251409.43306.sgrubb@redhat.com> (raw)
In-Reply-To: <4EA6F70D.9000509@fatpipeinc.com>
On Tuesday, October 25, 2011 01:51:09 PM Jason wrote:
> Thanks for your reply Steve. Our plan then is to install python on our
> development platform and compile audit with python support so we don't
> have to hack Makefiles.
I almost am done with hacking the makefiles. Just need to fix one thing in auparse/test
and I'll put it in svn.
> Then we will install audit on our network appliance which does not have python. Do
> you foresee any issues with doing it this way? What functionality do we lose by not
including python?
semanage, I think the selinux troubleshooter, and the audit log viewer are the only
things I know of that uses the python bindings.
-Steve
next prev parent reply other threads:[~2011-10-25 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 17:12 audit without python? Jason
2011-10-25 17:23 ` Steve Grubb
2011-10-25 17:31 ` Nathaniel Husted
2011-10-25 17:51 ` Jason
2011-10-25 18:09 ` Steve Grubb [this message]
2011-10-25 18:36 ` Steve Grubb
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=201110251409.43306.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=jason@fatpipeinc.com \
--cc=linux-audit@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox