From: Daniel J Walsh <dwalsh@redhat.com>
To: rarob@travelinglightfarm.net
Cc: selinux@tycho.nsa.gov
Subject: Re: PythonSELinux binding problem
Date: Fri, 22 Jul 2011 09:46:12 -0400 [thread overview]
Message-ID: <4E297F24.6090409@redhat.com> (raw)
In-Reply-To: <847d1fe893f5d55fda3cae11fb1c66df.squirrel@box559.bluehost.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/21/2011 05:33 PM, rarob@travelinglightfarm.net wrote:
> Hi, I'm using the python selinux bindings to determine if SELinux is
> disable/permissive/enforcing. The following snippet of code works
> just fine on RH5 and F10 regardless of the SELinux mode, but fails
> with an error on F11/12/13 and RH6 if SELinux is disabled.
>
> $ python -c 'import selinux ; print selinux.security_getenforce()'
>
> Under RH5 and F10 I correctly get the -1/0/1 returns for
> disabled/permissive/enforcing, as specified in the man pages for
> 'security_getenforce'. Under F11/12/13 and RH6 for permissive and
> enforcing I get the correct return values, but if the system is in
> disabled mode instead an OSError is thrown for 'No such file or
> directory'. I haven't look at the source for the underlying
> security_getenforce() system call, but I suspect is is assuming that
> the /selinux pseudo filesystem is populated (as in
> permissive/enforcing mode), and is not handling the case where that
> pseudo filesystem is empty.
>
> For now I've got my python calls wrapped in try/except blocks
> treating any exception as SELinux in disabled mode.
>
> I wasn't sure where the best place to log this as a bug is, either
> for the libselinux-python package or libselinux itself.
>
> -Rob
>
>
>
> -- 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.
We have modified python to act correctly when it receives and error from
the underlying C Library and throw an exception with the STDERR reported.
I do not believe this is a bug. And writing exception handling in
python is the correct behaviour, checking for -1 was the incorrect
behaviour from a python point of view.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEUEARECAAYFAk4pfyMACgkQrlYvE4MpobP4+ACbBvgfbP/yQt7lBk8HEQvNAO+O
LcoAl0RWJYGD3IJKEYsMK2NZe72fPEY=
=HGQR
-----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.
prev parent reply other threads:[~2011-07-22 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 21:33 PythonSELinux binding problem rarob
2011-07-22 13:44 ` Stephen Smalley
2011-07-22 14:00 ` Eric Paris
2011-07-22 13:46 ` Daniel J Walsh [this message]
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=4E297F24.6090409@redhat.com \
--to=dwalsh@redhat.com \
--cc=rarob@travelinglightfarm.net \
--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.