[Bug 1215179] New: /run/lock no longer belongs to the "lock" group; it is now in "root"
https://bugzilla.suse.com/show_bug.cgi?id=1215179 Bug ID: 1215179 Summary: /run/lock no longer belongs to the "lock" group; it is now in "root" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: David@WalkerStreet.info QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Sometime in the past few weeks, the ownership of /var/lock in Tumbleweed changed from root:lock to root:root, breaking OpenHAB3's ability to create lock files within that directory, unless it's given membership in the root group by adding "SupplementaryGroups=root" in its systemd .service configuration (which isn't the best security strategy). This problem is very similar to bug #552095, which was reported nearly 14 years ago and later resolved, although in a way that doesn't apply to my use case. What this change deliberate? If not, could it be reversed? If it can't be reversed, suggestions for a workaround would be appreciated. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215179 https://bugzilla.suse.com/show_bug.cgi?id=1215179#c4 Alexander Kulemin <filatovalex91@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |filatovalex91@gmail.com --- Comment #4 from Alexander Kulemin <filatovalex91@gmail.com> --- Another inconvenience introduced: minicom can't create lock file in /run/lock without root permissions. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com