[Bug 1221348] New: SELinux: relabeling after reboot is not communicated to user
https://bugzilla.suse.com/show_bug.cgi?id=1221348 Bug ID: 1221348 Summary: SELinux: relabeling after reboot is not communicated to user Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: jsegitz@suse.com Reporter: rfrohl@suse.com QA Contact: qa-bugs@suse.de CC: cathy.hu@suse.com Target Milestone: --- Found By: --- Blocker: --- Hi, if the SELinux policy is updated and the system reboots, the system gets relabeled. But this is not communicated to the user, it just looks like the system is stuck during boot. Especially with MicroOS the user might not know what was part of the last update. If the system is stuck during boot some users might not know that they use SELinux and where the wait is coming from. From a usability point of view: would it be possible to print a message that the system is currently relabeling the filesystem and maybe also add a message that it is done ? Second part might not be strictly needed, but I think some messaging might be helpful for users. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221348 https://bugzilla.suse.com/show_bug.cgi?id=1221348#c1 --- Comment #1 from Thorsten Kukuk <kukuk@suse.com> --- All startup messages are disabled by default... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221348 Thorsten Kukuk <kukuk@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kukuk@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1221348 https://bugzilla.suse.com/show_bug.cgi?id=1221348#c2 Johannes Segitz <jsegitz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jsegitz@suse.com |security-team@suse.de --- Comment #2 from Johannes Segitz <jsegitz@suse.com> --- putting back to the queue. Didn't know that this was assigned to me. We have that tracked as one of our low prio tasks and should be able to tackle it after holiday season -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com