Bug 1221348 - SELinux: relabeling after reboot is not communicated to user
Summary: SELinux: relabeling after reboot is not communicated to user
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Security (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Johannes Segitz
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-13 11:18 UTC by Robert Frohl
Modified: 2024-03-14 08:27 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Frohl 2024-03-13 11:18:07 UTC 
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.
Comment 1 Thorsten Kukuk 2024-03-14 08:26:57 UTC 
All startup messages are disabled by default...