Bug 703069

Summary: group writeable .so files in mailman package
Product: Red Hat Enterprise Linux 5 Reporter: Karel Srot <ksrot>
Component: mailmanAssignee: Jan Kaluža <jkaluza>
Status: CLOSED CURRENTRELEASE QA Contact: qe-baseos-daemons
Severity: low Docs Contact:
Priority: low    
Version: 5.6   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 703075 904144 (view as bug list) Environment:
Last Closed: 2013-03-13 17:10:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 703075, 703076, 904144    

Description Karel Srot 2011-05-09 08:09:01 UTC 
Description of problem:

# ls -lR /usr/lib/mailman/pythonlib/ | grep '\.so'
-rwxrwxr-x 1 root mailman 184980 Feb 21 08:51 _japanese_codecs.so
-rwxrwxr-x 1 root mailman  16060 Feb 21 08:51 hangul.so
-rwxrwxr-x 1 root mailman 467596 Feb 21 08:51 _koco.so

These file are not group writeable on RHEL6


Version-Release number of selected component (if applicable):
mailman-2.1.9-6.el5_6.1


There are also several python files group writeable under /usr/lib/mailman/pythonlib, I am not sure whether this is requred (same for RHEL6).
Comment 3 RHEL Program Management 2011-09-23 00:15:03 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.
Comment 4 RHEL Program Management 2012-06-12 01:05:38 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.
Comment 5 Jan Kaluža 2013-03-13 17:10:15 UTC 
Since RHEL5 is in Phase 2 and this bug is fixed in RHEL6, I'm closing this bug as CLOSED->CURRENTRELEASE.