[DSE-Dev] Bug#848232: semanage login: no awareness of exising entries

cgzones cgzones at googlemail.com
Sat Dec 17 17:18:48 UTC 2016

yes I am using libsepol1 2.6-2:

-- System Information:
Debian Release: stretch/sid
 APT prefers unstable
 APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages policycoreutils-python-utils depends on:
ii  libc6             2.24-8
ii  libselinux1       2.6-3
ii  libsepol1         2.6-2
ii  policycoreutils   2.6-2
ii  python3-audit     1:2.6.7-1
ii  python3-ipy       1:0.83-1
ii  python3-selinux   2.6-3
ii  python3-semanage  2.6-1
ii  python3-sepolgen  2.6-3
ii  python3-sepolicy  2.6-2
pn  python3:any       <none>
ii  selinux-utils     2.6-3

policycoreutils-python-utils recommends no packages.

policycoreutils-python-utils suggests no packages.

-- no debconf information

Can I test the upstream version by running
#sudo make LIBDIR=/usr/lib64 SHLIBDIR=/lib64 install install-pywrap
from the git repo inside a vm, or do I have to make more preparations
to really use only upstream dependencies?
I tried the upstream version without overwriting the system files, but
that does not solve the issue.
But I am not sure the upstream python modules were used, and probably
the system's libsepol was used too.

Kindly Regards,
     Christian Göttsche

2016-12-17 9:57 GMT+01:00 Laurent Bigonville <bigon at debian.org>:
> Le 15/12/16 à 14:13, cgzones a écrit :
> Hi,
>> When working on SELinux login settings, it seems that semanage is not
>> aware of already existing entries.
> Could you please try with libsepol1 2.6-2. I think this is a duplicate of
> #846484
> Regards,
> Laurent Bigonville

More information about the SELinux-devel mailing list