Bug 12438 - Permissions funnies
Summary: Permissions funnies
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sendmail   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
high
medium
Target Milestone: ---
Assignee: Florian La Roche
QA Contact:
URL:
Whiteboard:
Keywords: Security
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-06-18 19:14 UTC by Matthew Kirkwood
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-06-18 19:50:02 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 Matthew Kirkwood 2000-06-18 19:14:29 UTC
A few of perms oddities:

 * /usr/sbin/sendmail is setgid-root as well as setuid.
   Is there a reason for this?
 * Could we o-rx /var/spool/mqueue?
 * Can we restrict the use of /usr/bin/mailq to root?  I
   fail to understand why people should know who I'm
   sending email to.

Comment 1 Bill Nottingham 2000-06-18 19:33:46 UTC
Setting the permissions on mailq won't help if the user can still run
'sendmail -bp'; to change that requires patching sendmail.

Comment 2 Matthew Kirkwood 2000-06-18 19:50:01 UTC
Probably true.  mailq is just a symlink to sendmail anyway.

However, somewhere along the way (none of the Red Hat boxes I have access to run
sendmail :-) newaliases, which is also a symlink, got restricted, so it must be
doable.

Comment 3 Florian La Roche 2000-06-18 20:55:35 UTC
use restrictrunq and restrictmailq to change sendmail

I think it is good that any user can check the state of the sendmail
configuration, so I don't want to change perms.



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