Bug 158588 - saslauthd configured for pam fails authentication for yp users
saslauthd configured for pam fails authentication for yp users
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
rawhide
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-23 15:48 EDT by Thomas J. Baker
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: 1.23.16-7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-04 19:45:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
/var/log/audit/audit.log of errors (6.52 KB, text/plain)
2005-05-23 15:54 EDT, Thomas J. Baker
no flags Details

  None (edit)
Description Thomas J. Baker 2005-05-23 15:48:51 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050512 Fedora/1.0.4-2 Firefox/1.0.4

Description of problem:
When sendmail is set to authenticate to relay and saslauthd is set to use pam, I get selinux errrors authenticating yp users.

Version-Release number of selected component (if applicable):
cyrus-sasl-2.1.20-5, selinux-policy-targeted-1.23.16-6

How reproducible:
Always

Steps to Reproduce:
1.set up sendmail to authenticate to relay and saslauthd to use pam
2.try to send mail using a yp account
3.
  

Actual Results:  selinux prevents authentication

Expected Results:  authentication works and I can send mail.

Additional info:

dovecot it having similiar problems with authenticating yp users.
Comment 1 Thomas J. Baker 2005-05-23 15:54:28 EDT
Created attachment 114738 [details]
/var/log/audit/audit.log of errors

/var/log/audit/audit.log of errors
Comment 2 Daniel Walsh 2005-05-23 17:06:18 EDT
Fixed in selinux-policy-targeted-1.23.16-7

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