[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Access Control by group

To: openldap-software@openldap.org
Subject: Re: Access Control by group
From: Buchan Milne <bgmilne@staff.telkomsa.net>
Date: Mon, 29 Oct 2007 11:25:12 +0200
Cc: Jason Dearborn <jasondearborn@gmail.com>
Content-disposition: inline
In-reply-to: <4296d7270710261448j374395d1gf38cd54a5e0b13ef@mail.gmail.com>
References: <4296d7270710261330s328dff96sf0c2c1ab8a961404@mail.gmail.com> <4296d7270710261448j424b5ed8wf472d770cc668161@mail.gmail.com> <4296d7270710261448j374395d1gf38cd54a5e0b13ef@mail.gmail.com>
User-agent: KMail/1.9.6

On Friday 26 October 2007 23:48:49 Jason Dearborn wrote:
> Quanah pointed out we're running a pretty old version, which could be the
> culprit.  I know + signs in sets aren't supported.  I'm slightly less than
> enthusiastic about upgrading since we rely on LDAP+Samba groups. It's been
> a few years since I slogged through that implementation, but it may be time
> to revist.

I don't know why you think a client application would have problems after 
upgrading OpenLDAP, but I note that I am running our (minimally used - we 
have much more important things running against OpenLDAP) samba DC on RHEL4 
against OpenLDAP 2.3.

Please note that my packages allow you to run both the original RHEL4 2.2.13 
and my 2.3 packages in parallel if you want (e.g. on different IPs or ports), 
making it quite painless to "upgrade".

Regards,
Buchan

References:
- Access Control by group
  - From: "Jason Dearborn" <jasondearborn@gmail.com>
- Re: Access Control by group
  - From: "Jason Dearborn" <jasondearborn@gmail.com>

Prev by Date: Re: Replication Problem
Next by Date: LDAP provisioning error.
Index(es):
- Chronological
- Thread