Bug 12494 - /var/spool/mail should be 1777 -- Dupes 10678
Summary: /var/spool/mail should be 1777 -- Dupes 10678
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: imap (Show other bugs)
(Show other bugs)
Version: 6.2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Cristian Gafton
QA Contact:
: 21126 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2000-06-19 00:54 UTC by R P Herrold
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-06-19 00:54:58 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description R P Herrold 2000-06-19 00:54:57 UTC
The 'correct' permissions for /var/spool/mail _MUST_ be changed to 1777
here -- the owning package, in order to properly run the imapd.  See the
analysis on Bug 10678.

The 'taint' bit protects the lockfile, and false writes to mail spool
files, when combined with file ownerships.

Linuxconf also needs to have this change fed back to its maintainer as a
'correct' behavior.

As with other 7.0 changes, this is the RIGHT time to make this change.

Comment 1 Alan Cox 2000-08-05 01:52:08 UTC
1777 mail spool directory allows all sorts of unpleasant disk filling attacks,
people making symlinks into the mail spool and worse. Most mail applications are
not hardened against that kind of abuse.

Sure - there should be an sgid external mail-lock helper. I've been trying to
beat this into certain mail package authors for 3 or 4 years. But there isnt and
your cure is worse than the disease, far far worse than the disease

Comment 2 Mike A. Harris 2000-11-20 18:15:01 UTC
*** Bug 21126 has been marked as a duplicate of this bug. ***

Comment 3 Mike A. Harris 2000-11-20 18:16:31 UTC
*** Bug 21126 has been marked as a duplicate of this bug. ***

Comment 4 Mike A. Harris 2000-11-20 18:18:50 UTC
*** Bug 21126 has been marked as a duplicate of this bug. ***

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