Package: selinux-policy-default
Version: 2:2.20161023.1-9
Severity: normal
Dear Maintainer,
I tried setting up a tmpfs mount on a SELinux enabled system.
My fstab entry looks like this:
tmpfs /tmp rootcontext=system_u:object_r:tmp_t:s0 0 0
When I boot in permissive mode, this works as expected.
Package: selinux-policy-default
Version: 2:2.20161023.1-9
Severity: normal
Dear Maintainer,
the opendkim package (2.11.0~alpha-10+dep9u1) suggests that signing keys
should be stored in /etc/dkimkeys and sets up secure permission for that
directory.
The SELinux policy does not include filecontext
Package: selinux-policy-default
Version: 2:2.20161023.1-9
Severity: important
Dear Maintainer,
opendkim reads /usr/share/dns/root.key on startup.
However, the default SELinux policy has no rule to allow this.
I believe this breaks opendkim in enforcing mode.
Upstream refpolicy module 'dkim' incl
Package: policycoreutils-dev
Version: 2.6-3
Severity: important
Tags: patch upstream
Dear Maintainer,
running sepolgen may cause an exception, since it uses types that were
apparently removed from python 3.
For me, sepolgen only crashed when I had binutils installed, so this
does not render it co
Package: policycoreutils-dev
Version: 2.6-3
Severity: normal
Dear Maintainer,
sepolgen uses nm from the binutils package when analysing a binary.
If nm is not available, seplogen shows an error but works nonetheless,
but probably produces less useful output (I didn't check
systematically).
I sug
a thing. Only unloading (disabling) the
plugin altogether avoids crashing pidgin on close.
Can I provide further information, tests or action?
yours sincerly,
Sebastian
--
Sebastian Hamann
Software Engineer
=
MCS Moorbek Computer Systeme GmbH
Es
(>= 2.12.0) | 2.12.1-1
libgtkspell0 (>= 2.0.2) | 2.0.10-3+b1
libice6 (>= 1:1.0.0) | 2:1.0.4-1
libpango1.0-0 (>= 1.18.3) | 1.18.4-1
libpurple0 (>= 2.3.0) | 2.3.1-2
libsm6
7 matches
Mail list logo
