From: Sven Vermeulen <sven.vermeulen@siphos.be>
To: selinux@tycho.nsa.gov
Subject: Trying to support Python 3 but fails on libsemanage
Date: Wed, 16 May 2012 11:17:36 +0200 [thread overview]
Message-ID: <20120516091736.GA10721@siphos.be> (raw)
I'm trying to get Python 3 support up and going with the SELinux userspace
utilities. I'm hitting a compatibility issue that I'm not able to work out
further.
This is the following "test case":
semanage fcontext -a -t swapfile_t /swapfile
semanage fcontext -d -t swapfile_t /swapfile
With Python 2.7, this works as it should be. With Python 3.2 however, I get
the following error while trying to delete the entry:
/usr/sbin/semanage: File context for /swapfile is not defined
The entry is correctly available in the file_contexts.local file. Also, if I
switch from Python 3.2 to 2.7 after adding the entry (but before removing),
removing the entry works as it should be.
I notice that semanage calls seobject.py which calls semanage.py. All these
files are exactly the same (no changes made to those), so I guess it is
something to do within the _semanage.so file.
Now, this is a library created through swig magic, which i'm totally unknown
to. It looks like all code is C-based, and then transformed into a
Python-compatible call, not?
Is there anyone already running the SELinux userspace tools with Python 3?
If so, how do you build libsemanage (as that provides the _semanage.so
file)?
Wkr,
Sven Vermeulen
--
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 reply other threads:[~2012-05-16 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 9:17 Sven Vermeulen [this message]
2012-05-17 16:25 ` Trying to support Python 3 but fails on libsemanage Daniel J Walsh
2012-05-18 11:22 ` Sven Vermeulen
2012-05-23 20:35 ` Sven Vermeulen
2012-05-26 16:44 ` Sven Vermeulen
2012-05-31 20:59 ` Eric Paris
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=20120516091736.GA10721@siphos.be \
--to=sven.vermeulen@siphos.be \
--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.