From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Patch to add python audit2why bindings.
Date: Wed, 23 Jan 2008 13:39:31 -0500 [thread overview]
Message-ID: <479789E3.3060007@redhat.com> (raw)
In-Reply-To: <1201098728.7025.270.camel@moss-spartans.epoch.ncsc.mil>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stephen Smalley wrote:
> On Fri, 2008-01-11 at 11:03 -0500, Daniel J Walsh wrote:
> Updated policycoreutils will be coming to take advantage of these bindings.
>
> setroubleshoot will also.
>
> import selinux
>
> will work the way it always did, but now you can execute
>
> import selinux.audit2allow as audit2allow
>
> audit2allow.init()
>
> for i in avc:
> print audit2allow.analyze(i.scon, i,tcon, i,class, i.access)
>
> audit2allow.finish()
>
> And get the reason for the AVC.
>
>> The Makefile changes are broken:
>> make DESTDIR=~/obj install install-pywrap > outinstall: accessing
>> `/home/sds/obj/usr/lib/python2.5/site-packages/selinux/__init__.py': Not
>> a directory
>> make[1]: *** [install-pywrap] Error 1
>> make: *** [install-pywrap] Error 2
>
Works for me?
THis directory should have been created by the Makefile?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkeXieMACgkQrlYvE4MpobMuDQCfajj6hcQlfjwWasgsv9lLfKcS
b7wAoL+EWV3I1K/6FTmB9PPFLoaoW4dd
=9Twz
-----END PGP SIGNATURE-----
--
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:[~2008-01-23 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 16:03 Patch to add python audit2why bindings Daniel J Walsh
2008-01-23 14:32 ` Stephen Smalley
2008-01-23 18:39 ` Daniel J Walsh [this message]
2008-01-23 18:47 ` Stephen Smalley
2008-01-23 21:00 ` Stephen Smalley
2008-01-29 10:30 ` Václav Ovsík
2008-01-29 13:19 ` 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=479789E3.3060007@redhat.com \
--to=dwalsh@redhat.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.