Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 157768 - Squirrelmail doesn't like SElinux - messages lost
Summary: Squirrelmail doesn't like SElinux - messages lost
Alias: None
Product: Fedora
Classification: Fedora
Component: squirrelmail
Version: 3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Warren Togami
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-05-14 20:48 UTC by P Fudd
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-05-31 04:46:29 UTC

Attachments (Terms of Use)

Description P Fudd 2005-05-14 20:48:09 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922

Description of problem:
Squirrelmail can't send email due to restrictive selinux policy.

Typing 'setenforce 0' allows squirrelmail to work.

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

How reproducible:

Steps to Reproduce:
1. Install fresh Fedora Core 3 system with selinux enabled (includes squirrelmail)
2. Fix /etc/httpd/conf/httpd.conf to use index.php as a directory index
3. Go to http://localhost/webmail
4. Log in, compose message to yourself
5. Send it
6. Check log to find out why message disappeared into thin air

Actual Results:  Found entries like this in the log:
May 14 11:25:41 dan kernel: audit(1116095141.399:0): avc:  denied  { read } for  pid=5643 exe=/usr/sbin/httpd name=sh dev=dm-0 ino=2616329 scontext=user_u:system_r:httpd_t tcontext=system_u:object_r:bin_t tclass=lnk_file

Expected Results:  Email should be sent.

Additional info:

System is configured to use sendmail.

I tried a different policy file (selinux-policy-targeted-1.17.30-3.6) but the errors don't go away, they only change.

Comment 1 Warren Togami 2005-05-14 21:08:43 UTC
Are you sure the filesystem is properly labeled?

If it is, then this may be a policy problem...

Comment 2 Daniel Walsh 2005-05-14 22:38:04 UTC
It is allowed in the 3.6 policy
> grep bin_t:lnk_ apache.te
allow httpd_t bin_t:lnk_file read;

Are you sure you have it loaded?

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