Bug 49818
| Summary: | /var/lock has incorrect ownership | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | greg hosler <greg> |
| Component: | filesystem | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED NOTABUG | QA Contact: | Aaron Brown <abrown> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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: | --- | Target Upstream Version: | |
| Embargoed: | |||
This is intentional. Group writable /var/lock introduces too many security concerns. |
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.