Bug 1226807 - minicom cannot run as user due to /run/lock permissions
Summary: minicom cannot run as user due to /run/lock permissions
Status: NEW
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Other (show other bugs)
Version: Leap 15.6
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Simon Lees
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-22 06:36 UTC by Aaron Williams
Modified: 2024-07-01 06:35 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Williams 2024-06-22 06:36:09 UTC
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-var-lock-lockdev 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.