Bug 457388

Summary:	Please don't call "/usr/bin/python" from /etc/cron.d/mailman
Product:	[Fedora] Fedora	Reporter:	Jan Kratochvil <jan.kratochvil>
Component:	mailman	Assignee:	Tomas Smetana <tsmetana>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-07-31 12:33:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	129920
Bug Blocks:

Description Jan Kratochvil 2008-07-31 11:10:44 UTC

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

Description of problem:
In SE Linux the program that is executed determines the domain that the program
is run in.

Running "/usr/bin/python -S /usr/lib/mailman/cron/cull_bad_shunt" from
/etc/cron.d/mailman causes the cron job to run in domain sysadm_crond_t, while
running it as "/usr/lib/mailman/cron/cull_bad_shunt" (with the first line of the
script being "#!/usr/bin/python -S") causes it to run in domain mailman_queue_t
(really this one? Jan K.) which is the desired result (*).

This change will not have any affect for people who don't use SE Linux and will
do a lot of good for SE Linux users.

Version-Release number of selected component (if applicable):
mailman-2.1.11-2.fc10.x86_64
(this line was not present in mailman-2.1.9-10.fc9.x86_64)

How reproducible:
Always

Steps to Reproduce:
examine /etc/cron.d/mailman

Additional info:
I do not run SELinux so I know nothing if it is a problem.
Just IMO it is as I saw the old bug and the current file content.
Sorry if it works in SELinux.

Comment 1 Tomas Smetana 2008-07-31 11:45:33 UTC

You're right.  This doesn't seem to be OK.  I didn't see any AVC messages caused
by this yet but the shunt and bad queues are usually empty on my system...

Thanks.

Comment 2 Tomas Smetana 2008-07-31 12:33:49 UTC

Mailman-2.1.11-3 should solve the problem.  Please reopen the bug if not.