Bug 700777 - too open perms on directories
Summary: too open perms on directories
Keywords:
Status: CLOSED DUPLICATE of bug 704699
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mailman
Version: 6.0
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Kaluža
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 701539
TreeView+ depends on / blocked
 
Reported: 2011-04-29 11:19 UTC by Florian La Roche
Modified: 2011-06-02 19:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 701539 (view as bug list)
Environment:
Last Closed: 2011-06-02 19:43:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Florian La Roche 2011-04-29 11:19:38 UTC
Description of problem:

In RHEL6 mailman, the directory /usr/lib/mailman/cgi-bin
has perms 2775 with set-group-id apps inside this directory
which have perms 2755.

Shouldn't the directory also have the write-group perm
removed?

E.g. sendmail is checking for this condition and does not trust
the applications inside this dir.

best regards,

Florian La Roche




Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 RHEL Program Management 2011-04-29 11:47:36 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Jan Kaluža 2011-05-02 11:10:49 UTC
You're right, that directory should not have write-group perm.


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