Bug 4084 - Minicom won't run unless run as root
Summary: Minicom won't run unless run as root
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: minicom   
(Show other bugs)
Version: 6.0
Hardware: i386 Linux
low
low
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-07-17 06:45 UTC by antonino
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-07-28 18:34:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

Description antonino 1999-07-17 06:45:04 UTC 
Minicom fails unless it's run with root
privileges. As a normal user it fails to create
the lock file in /var/lock/LCK..modem.

The -o option does not override it. Is this a security
feature?
Comment 1 Jeff Johnson 1999-07-28 18:34:59 UTC 
Minicom is shipped without the setgid bit needed to write in
/var/lock in order to minimize security risks. If you do
	chgrp uucp /usr/bin/minicom
	chmod g+s /usr/bin/minicom
then any user (not just root) will be able to create a lock file.
Note You need to log in before you can comment on or make changes to this bug.