[Bug 218899] Re: upgrade to hardy: user openldap is not added to group sasl

2008-09-02 Thread Mathias Gug
** Changed in: openldap (Ubuntu) Importance: Undecided => Low Status: Confirmed => Triaged -- upgrade to hardy: user openldap is not added to group sasl https://bugs.launchpad.net/bugs/218899 You received this bug notification because you are a member of Ubuntu Server Team, which is sub

[Bug 218899] Re: upgrade to hardy: user openldap is not added to group sasl

2008-09-02 Thread Mathias Gug
** Changed in: openldap (Ubuntu) Status: New => Triaged ** Changed in: openldap2.3 (Ubuntu Hardy) Importance: Undecided => Low Status: New => Triaged ** Changed in: openldap (Ubuntu) Status: Triaged => Confirmed -- upgrade to hardy: user openldap is not added to group sa

[Bug 218899] Re: upgrade to hardy: user openldap is not added to group sasl

2008-08-29 Thread Mathias Gug
** Also affects: openldap (Ubuntu) Importance: Undecided Status: New ** Changed in: openldap2.3 (Ubuntu) Status: Confirmed => Invalid ** Changed in: openldap (Ubuntu Hardy) Status: New => Invalid -- upgrade to hardy: user openldap is not added to group sasl https://bugs.

[Bug 218899] Re: upgrade to hardy: user openldap is not added to group sasl

2008-06-06 Thread Martin Emrich
+1 for _not_ using saslauthd. The first option only changes one line in /etc/group, but using saslauthd would require having another daemon running. Furthermore, saslauthd recommends against using the sasldb backend (see saslauthd(8) for details). -- upgrade to hardy: user openldap is not added

[Bug 218899] Re: upgrade to hardy: user openldap is not added to group sasl

2008-06-06 Thread Philipp Kaluza
I can confirm this. While this setup doesn't seem too common, it's certainly a valid and supported one. This needs to be adressed on the slapd side, so reassigning this. The suggested fix (adduser openldap sasl) is quite simple, won't cause any regressions, but does give the slapd process some m

[Bug 218899] Re: upgrade to hardy: user openldap is not added to group sasl

2008-04-28 Thread Martin Emrich
Hi! I have a pretty simple setup with libnss-ldap and libpam-ldap authenticating a locally running slapd, which in turn authenticates against sasldb. I have no saslauthd or so running. Before upgrading from dapper to hardy, slapd ran as root, and thus was able to access /etc/sasldb2. After the

[Bug 218899] Re: upgrade to hardy: user openldap is not added to group sasl

2008-04-28 Thread Chuck Short
Hello, Can you provide more information about your setup? Thanks chuck ** Changed in: cyrus-sasl2 (Ubuntu) Status: New => Incomplete -- upgrade to hardy: user openldap is not added to group sasl https://bugs.launchpad.net/bugs/218899 You received this bug notification because you are a

[Bug 218899] Re: upgrade to hardy: user openldap is not added to group sasl

2008-04-25 Thread Chuck Short
** Changed in: cyrus-sasl2 (Ubuntu) Sourcepackagename: openldap2.3 => cyrus-sasl2 -- upgrade to hardy: user openldap is not added to group sasl https://bugs.launchpad.net/bugs/218899 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sa