Bug 49818 - /var/lock has incorrect ownership
Summary: /var/lock has incorrect ownership
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: filesystem   
(Show other bugs)
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-07-24 12:37 UTC by greg hosler
Modified: 2014-03-17 02:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-07-24 12:37:44 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)

Description greg hosler 2001-07-24 12:37:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.6-2smp i686; Nav)

Description of problem:
/var/lock is used by uucp, among others, to write lock files into.
Specifically, uucico (of uucp), will write temp PID files into
/var/lock. uucico runs suid/sgid uucp.uucp - /var/lock needs to
be group owned uucp, otherwise uucp (and other SGID applications which
should also be group uucp owned) which need to create/check tmp PID
files will fail.


How reproducible:
Always

Steps to Reproduce:
1. ls -l /var | grep lock
2.
3.
	

Actual Results:  drwxr-xr-x    6 root     root         1024 Jul 24 20:52
lock


Expected Results:  drwxrwxr-x    6 root     uucp         4096 Jul 24 20:45
lock

    ^^^                  ^^^^

Additional info:

as a reference, check RH7.1 and all earlier releases.

Comment 1 Bill Nottingham 2001-07-24 21:16:39 UTC
This is intentional. Group writable /var/lock introduces too many security concerns.


Note You need to log in before you can comment on or make changes to this bug.