Bug 703076

Summary:	group writeable .so files in mailman package
Product:	Red Hat Enterprise Linux 6	Reporter:	Jan Kaluža <jkaluza>
Component:	mailman	Assignee:	Jan Kaluža <jkaluza>
Status:	CLOSED WORKSFORME	QA Contact:	qe-baseos-daemons
Severity:	low	Docs Contact:
Priority:	low
Version:	6.2	CC:	jkaluza, ksrot
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	703075	Environment:
Last Closed:	2011-05-09 13:27:19 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:	703069, 703075, 904144
Bug Blocks:

Description Jan Kaluža 2011-05-09 08:35:34 UTC

+++ This bug was initially created as a clone of Bug #703075 +++

+++ This bug was initially created as a clone of Bug #703069 +++

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 2 RHEL Program Management 2011-05-09 09:08:18 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.