New F42 selinux-policy build
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2025-dde3c4a0f1Please log in to add feedback.
This update has been submitted for testing by zpytela.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Seems to be working fine.
This update has been pushed to testing.
I can't really say if it relabels the filesystem. all I can say is, that the box boots twice with /.autorelabel and that /.autorelabel is removed afterwards.
how could one check if relabeling is working ? all I know is: sudo journalctl -b0|grep -i relabel => Aug 11 04:04:44 obelix.fritz.box systemd[1]: Relabeled /dev/, /dev/shm/, /run/ in 6.741ms. Aug 11 04:04:45 obelix.fritz.box systemd[1]: selinux-autorelabel-mark.service - Mark the need to relabel after reboot was skipped because of an unmet condition check (ConditionSecurity=!selinux).
ideas ?
Relabeling works again.
journalctl -b -1 -g relabel -l --no-pagerThis update can be pushed to stable now if the maintainer wishes
no regressions noted
in general it works fine, but I'm still having issues with VMs (SELinux is preventing rpc-virtqemud from accessing or writing to the file...)
I also have this message at log:
ok for me
This update has been submitted for stable by bodhi.
@sixpack13 try this:
cp -a /usr/sbin/agetty /usr/sbin/agetty.tmp
restorecon -vn /usr/sbin/agetty.tmp
Would relabel /usr/bin/agetty.tmp from system_u:object_r:getty_exec_t:s0 to system_u:object_r:bin_t:s0
fixfiles -F onboot
systemctl reboot
restorecon -vn /usr/sbin/agetty.tmp
rm /usr/sbin/agetty.tmp
@geraldosimiao There was no virtqemud-related change in the last buid
@zpytela
thanks it seems to work now: Aug 11 17:18:59 obelix.fritz.box systemd[1]: Starting selinux-autorelabel.service - Relabel all filesystems...
@zpytela yeah, this regression started since the last policy upgrade.
This update has been pushed to stable.
@geraldosimiao please file a bz, I am not aware of any problem which could have been added by the last build