[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: [ldapext] [Fwd: LDAP C API gripes]
- To: idra@samba.org
- Subject: Re: [ldapext] [Fwd: LDAP C API gripes]
- From: Pierangelo Masarati <ando@sys-net.it>
- Date: Wed, 22 Aug 2007 11:50:51 +0200
- Cc: ldapext@ietf.org
- In-reply-to: <1172084828.11482.53.camel@localhost.localdomain>
- References: <45D251C0.2050306@highlandsun.com> <45DC6997.5020906@highlandsun.com> <1172073139.11482.11.camel@localhost.localdomain> <45DC6CCF.6060100@highlandsun.com> <1172074277.11482.17.camel@localhost.localdomain> <20070221125226.3e54fb9e.mba2000@ioplex.com> <45DC9414.7010706@sys-net.it> <1172084828.11482.53.camel@localhost.localdomain>
- User-agent: Thunderbird 1.5.0.8 (X11/20061025)
simo wrote:
There __is__ a standard way, it's described in RFC4512 secton 4.4; the
fact that some implementors don't comply with it, or do not populate
values as indicated in the standard is a totally different business.
Last I checked AD supported subschemaSubentry, I don't think that
changed overnight. I can't say the same of the std openLdap installation
you find on many distributions out there :)
Sorry, I missed this. OpenLDAP supports subschemaSubentry since 2.0,
June 2000. It is, of course, an operational attribute and, as such, it
must be explicitly requested by clients (RFC2251, A.D. 1997). The fact
that others don't comply with this requirement is not OpenLDAP's
business. If in 2007 there's still distros running OpenLDAP 1.X, well,
they have more urgent things to care about than subschemaSubentry.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
---------------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Email: pierangelo.masarati@sys-net.it
---------------------------------------
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext