Matthew Saltzman wrote:
I ran up2date to get selinux-policy-targeted-1.27.1-2.1.noarch.rpm.
up2date hung for a very long time at the end of the installation, so
finally, I killed it. At that point, I had two versions of
selinux-policy-targeted installed. Verifying each showed that all the
files were correct for the new version. But just to be safe (oops), I
deleted both and tried to reinstall
selinux-policy-targeted-1.27.1-2.1.noarch.rpm.
Running up2date now produces:
# up2date
Could not set exec context to root:sysadm_r:rpm_t.
I am updating the policy to put this role back in. Will
/usr/sbin/up2date work?
and fails to run. After setenforce 0, I still get the message and
up2date runs.
Forcing a reinstall of selinux-policy-targeted-1.27.1-2.1.noarch.rpm
has no effect. Rebooting has no effect. Relabeling on reboot has no
effect.
(Actually, after relabeling, rpm --verify produces
# rpm --verify selinux-policy-targeted
S.5....T. /etc/selinux/targeted/contexts/files/file_contexts.homedirs
)
So far, other things appear to work normally, but up2date does not work.
How can I fix this?
Thanks.
Messages in audit.log are:
type=USER_AUTH msg=audit(1127508331.874:1624469): user pid=3328 uid=0
auid=4294967295 msg='PAM authentication: user=root
exe="/usr/sbin/userhelper" (hostname=?, addr=?, terminal=?
result=Success)'
type=USER_ACCT msg=audit(1127508331.874:1624478): user pid=3328 uid=0
auid=4294967295 msg='PAM accounting: user=root
exe="/usr/sbin/userhelper" (hostname=?, addr=?, terminal=?
result=Success)'
type=USER_START msg=audit(1127508331.884:1626823): user pid=3328 uid=0
auid=4294967295 msg='PAM session open: user=root
exe="/usr/sbin/userhelper" (hostname=?, addr=?, terminal=?
result=Success)'
type=USER_END msg=audit(1127508331.901:1627077): user pid=3328 uid=0
auid=4294967295 msg='PAM session close: user=root
exe="/usr/sbin/userhelper" (hostname=?, addr=?, terminal=?
result=Success)'
--
--
fedora-selinux-list mailing list
fedora-selinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-selinux-list
