Hi folks,
i have noticed openldap keeps releasing new versions from time to
time. I have not noticed changes in protocol specification. So why
does openldap release new versions ? Isn't it mature enough yet ? I am
asking cause i am used to djb tools like qmail and djbdns and they
don't change
Kurt Zeilenga wrote:
On Aug 4, 2012, at 9:08 AM, Howard Chu h...@symas.com wrote:
Dora Paula wrote:
Iiuc, your acl permit search ( There are any entries of question type
in term of search filter) to any authenticated user. If the user is
also member of the group grant also read privilege
On Aug 05, 2012, at 08.07, Friedrich Locke wrote:
Hi folks,
i have noticed openldap keeps releasing new versions from time to
time. I have not noticed changes in protocol specification. So why
does openldap release new versions ? Isn't it mature enough yet ? I am
asking cause i am used to
I am not a openldap developer but i am a lazy FL / oss developer. So i
think your question is general. There are so many project that don't
change the basic function but are releasing new version. Why ? Well, a
possibility is introducing a new build sistem, changing the library
api for a better
Howard Chu wrote:
Kurt Zeilenga wrote:
On Aug 4, 2012, at 9:08 AM, Howard Chuh...@symas.com wrote:
I haven't looked at the code yet but it's possible this is a bug.
Not a bug. As documented, every access statement ends implicitly with a by *
none clause.
Ah right. The continue control is
I have a requirement to support personalization. I didn't find many
articles to do that. Please point me some of the articles related to it.
-Jignesh
On Aug 5, 2012, at 1:58 PM, Dora Paula dee...@gmx.net wrote:
Another (at least to me much better) solution seems to be to get rid of the
implicit by * none code:
It represents neither a reasonable security functionality, nor a valueable
convenience feature - the opposite seems true:
