[Bug 64425] Re: winbindd_privileged permission issue

2014-03-20 Thread Thomas C.
ok, this one is the right solution: gpasswd -a proxy winbindd_priv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/64425 Title: winbindd_privileged permission issue To manage notifications about thi

[Bug 64425] Re: winbindd_privileged permission issue

2014-03-19 Thread Thomas C.
thats my quick fix: /etc/init/winbind-squid.conf start on started squid3 task script chgrp -R proxy /var/lib/samba/winbindd_privileged/ chgrp -R proxy /var/run/samba/winbindd_privileged/ end script -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 64425] Re: winbindd_privileged permission issue

2008-03-12 Thread Ready
To winbind to use, I have the user in the secondary group winbindd_priv added. Now, have squid read right users on the folder /var/run/samba/winbindd_privileged. Unfortunately, I do but still this error message "Ensure permissions on / var / run / samba / winbindd_privileged are set correctly."

[Bug 64425] Re: winbindd_privileged permission issue

2007-09-06 Thread Jerome Haltom
I take back what I previously said. NSS does not use this pipe, it uses another pipe I was unaware of. -- winbindd_privileged permission issue https://bugs.launchpad.net/bugs/64425 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

[Bug 64425] Re: winbindd_privileged permission issue

2007-08-07 Thread Jerome Haltom
Except that's not true. All regular users must be able to look up their own record. Otherwise they cannot map their known uid to a displayable username. This happens all the time (everytime you run ls or ps, constantly by gnome applications themselves.) -- winbindd_privileged permission issue htt

[Bug 64425] Re: winbindd_privileged permission issue

2007-08-07 Thread Ante Karamatić
Ummm... no? That's not solution, authentication and authorization is done by system (root), not users. You should add to this group only users under which some service is run - like squid. winbindd(8) describes your setup under 'EXAMPLE SETUP', if that's what you had in mind. -- winbindd_privil

[Bug 64425] Re: winbindd_privileged permission issue

2007-08-07 Thread Jerome Haltom
I don't think this solution really works in my circumstance, which is that I use Winbind with PAM/NSS for *all* user's logons. Because my systems are joined to a domain and are standard desktop machines. I would need to add *all* users to this group. This is not very practical. It seems my use ca

[Bug 64425] Re: winbindd_privileged permission issue

2007-08-04 Thread Ante Karamatić
Snip from init script in gutsy: case "$1" in start) log_daemon_msg "Starting the Winbind daemon" "winbind" mkdir -p /var/run/samba/winbindd_privileged || return 1 chgrp winbindd_priv $PIDDIR/winbindd_privileged/ || return 1 c