[Bug 1204860] New: Installed selinux on fresh install: no labeling, got locked out
http://bugzilla.opensuse.org/show_bug.cgi?id=1204860 Bug ID: 1204860 Summary: Installed selinux on fresh install: no labeling, got locked out Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team@suse.de Reporter: opensuse.k1akb@slmail.me QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I am not sure if this is still an issue, but I want to make sure it is known. I have an issue which *seems to be* described here: # 1199520. I am not sure if this is exactly the same issue/consequence/solution, so I would like to leave this information to be sure. I installed selinux soon after a fresh installation of OpenSUSE Tumbleweed: first installed selinux and the 'targeted' profile, then realized I was missing a component so I installed selinux-targeted-setup. After rebooting, I was locked out of the system, presumably because access to the shell was denied to all users. (At this point no relabeling had taken place.) I could not fix this with 'restorecon -Rv /', because this was an NOOP execution. I am not sure why, I do not know selinux well enough, the command just immediately exits. Then I noticed that '/etc/selinux/.autorelabel' was created -- and still existed -- and moved this to '/' and on next boot the relabeling process started and the issue resolved itself. From then on, I have not encountered any (noticable) issues. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204860 OpenSUSE Account <opensuse.k1akb@slmail.me> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Installed selinux on fresh |Installed selinux (after |install: no labeling, got |fresh install): no |locked out |labeling, got locked out -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204860 http://bugzilla.opensuse.org/show_bug.cgi?id=1204860#c2 --- Comment #2 from OpenSUSE Account <opensuse.k1akb@slmail.me> --- It exists, see https://build.opensuse.org/package/show/openSUSE:Factory/selinux-targeted-se... I cannot make your proposed changes, because as mentioned, I fixed the problem by moving the `.autorelabel` file. I can confirm that your changes to `/etc/selinux/config` were correctly applied. (Both the proper policy and enforcement was enabled.) The kernel had booted with selinux being enforced, because it locked me out of the system because of that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204860 http://bugzilla.opensuse.org/show_bug.cgi?id=1204860#c3 --- Comment #3 from OpenSUSE Account <opensuse.k1akb@slmail.me> --- Also, the `mv` command in the `selinux-targeted-setup.spec` file does not make sense to me. The only thing I can say is that it worked when I moved `.autorelabel` back to `/`. (See <https://build.opensuse.org/package/view_file/openSUSE:Factory/selinux-targeted-setup/selinux-targeted-setup.spec?expand=1>) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204860 http://bugzilla.opensuse.org/show_bug.cgi?id=1204860#c4 Johannes Segitz <jsegitz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jsegitz@suse.com |alexandre.vicenzi@suse.com --- Comment #4 from Johannes Segitz <jsegitz@suse.com> --- Interesting, I've never heard of this package. I'll assign it to the initial author -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204860 http://bugzilla.opensuse.org/show_bug.cgi?id=1204860#c6 --- Comment #6 from OpenSUSE Account <opensuse.k1akb@slmail.me> --- To clarify: I am new to this distribution. The package seemed like the obvious way to go. I will keep an eye out of "patterns" as these are apparently called in SUSE. I noticed that they correspond with the "groups"/"main categories" (if I may call them that) of YaST Software Management. The "dubious package" in question is part of the SUSE ecosystem. There is no clear difference for me. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com