Bug 231811 - Incorrect File permissions on /var/cache/samba/winbind
Incorrect File permissions on /var/cache/samba/winbind
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: samba (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Simo Sorce
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-12 05:23 EDT by Jóhann B. Guðmundsson
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-12 08:18:44 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)

  None (edit)
Description Jóhann B. Guðmundsson 2007-03-12 05:23:46 EDT
Description of problem:

Came incorrect with samba-3.0.10-1.4E.11 packages
RHEL 4

Error log showed

nsswitch/winbindd_pam.c:winbindd_pam_auth_crap(429)  winbindd_pam_auth_crap:
non-privileged access denied.  !  winbindd_pam_auth_crap: Ensure permissions on
/var/cache/samba/winbindd_privileged are set correctly.
Version-Release number of selected component (if applicable):


How reproducible:
User authenticating through Freeradius got denied 
When they were authenticating with Freeradius + Samba setup that involved winbind 

Steps to Reproduce:
1. Trying to authenticate 
2.
3.
  
Actual results:
File permission on /var/cache/samba/winbind was 0750

Expected results:
Should have been 0755

Additional info:

This setup was pptp + freeradius + samba ( pptp vpn setup )
Ensure next time that user rights on samba work for varios samba deployments
( Cups + Point 'N'Print, Freeradius + Samba + AD, Freeradius + samba + Winbind etc.)

Users of other service need to have access to samba.
Comment 1 Simo Sorce 2007-03-12 08:18:44 EDT
Sorry jonathan, but the winbindd_privileged pipe is not supposed to be readable
by everyone. To let a daemon use it you must add the user it runs with to the
group owner of the privileged pipe.
Winbindd will not let you use the pipe if it is readable by everyone.

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