[Bug 1226807] New: minicom cannot run as user due to /run/lock permissions

https://bugzilla.suse.com/show_bug.cgi?id=1226807 Bug ID: 1226807 Summary: minicom cannot run as user due to /run/lock permissions Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: aaron.w2@gmail.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- When running minicom as a user in the dialout group I now get an error message that it cannot create a lock file. This worked in 15.5. Minicom is attempting to create the lockfile in /run/lock but only root has write access to this directory. Minicom uses lockdev which requires access to /var/lock. One way to fix this is to build minicom without lockdev. Lockdev is fundamentally broken because it requires write access to /run/lock, which is a security nightmare. When minicom is built without lockdev the location of the lockfiles can be specified to be someplace other than /var/lock. See https://systemd-devel.freedesktop.narkive.com/vCJLfMo2/headsup-var-lock-and-... for a discussion. As an interim solution, I added an ACL to allow the dialout group to write to /run/lock, though this is far from ideal. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226807 https://bugzilla.suse.com/show_bug.cgi?id=1226807#c3 Jaan Rebane <jaan_r@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jaan_r@yahoo.com --- Comment #3 from Jaan Rebane <jaan_r@yahoo.com> --- A forum post about this: https://forums.opensuse.org/t/not-able-to-create-minicom-lockfile-as-user/17... In short: It seems like group for /run/lock folder was changed, now it's root, it used to be lock. (User should still be in dialout group for this to work.) If there is a reason why it has to be in root group, there should be another fix. My temporary fix that worked was: sudo cp /usr/lib/tmpfiles.d/systemd-suse.conf /etc/tmpfiles.d/ sudo nano /etc/tmpfiles.d/systemd-suse.conf # Changed line 10 from d /run/lock 0775 root root - # to d /run/lock 0775 root lock - -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226807 https://bugzilla.suse.com/show_bug.cgi?id=1226807#c4 --- Comment #4 from Jaan Rebane <jaan_r@yahoo.com> --- I'll mention here some related bug reports: https://bugzilla.opensuse.org/show_bug.cgi?id=1212801 (suggestion to drop lockdev) https://bugzilla.opensuse.org/show_bug.cgi?id=1222505 (ckermit not working) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226807 Peter Münster <pmlists@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmlists@free.fr -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com