openldap-bugs

openldap-bugs@openldap.org

1 participants
20997 discussions

Re: (ITS#6828) TLS fails to start when LDAP_OPT_CONNECT_ASYNC is used
by hyc＠symas.com 09 Jun '11

09 Jun '11

ipuleston(a)SonicWALL.com wrote: > The patch that I submitted above has a memory leak due not freeing "ber" when returning error LDAP_X_CONNECTING from function ldap_send_initial_request(). I have uploaded a new version of the patch with this fixed to ftp.openldap.org/incoming as ian-puleston-110412.patch.2 (note the .2 on the end - it was a 2nd attempt after I forgot to specify ASCII mode). Unfortunately the patch was made against 2.4.23 and not against HEAD. It does not apply cleanly to current git. Patches must always be submitted against the development code, not against released code. I'm pretty sure that this chunk can never do anything useful. diff -u libldap.orig/request.c libldap/request.c --- libldap.orig/request.c 2010-06-10 10:39:48.000000000 -0700 +++ libldap/request.c 2011-04-12 12:11:20.769166100 -0700 @@ -446,7 +462,21 @@ lc->lconn_server = ldap_url_dup( srv ); } - lc->lconn_status = async ? LDAP_CONNST_CONNECTING : LDAP_CONNST_CONNECTED; + if ( async ) { +#ifdef HAVE_TLS + void *ssl = NULL; + ber_sockbuf_ctrl( lc->lconn_sb, LBER_SB_OPT_GET_SSL, (void *)&ssl ); + if ( ssl ) { + /* the connect finished and tls was started */ + lc->lconn_status = LDAP_CONNST_CONNECTED; + } else +#endif + { + lc->lconn_status = LDAP_CONNST_CONNECTING; + } + } else { + lc->lconn_status = LDAP_CONNST_CONNECTED; + } #ifdef LDAP_R_COMPILE ldap_pvt_thread_mutex_lock( &ld->ld_conn_mutex ); #endif The connection has just been created, asynchronously, so there's no way that the TLS layer was already started when it got here. Also, even if this was valid, it obviously would only apply for OPT_X_TLS_HARD || ldaps, but you haven't checked that condition here. Ultimately it appears that this test is a no-op. Also, I suggest that you only check for CONNST_CONNECTING in the callers, and do the TLS check in the check function, like this: +int +ldap_int_check_async_open( LDAP *ld, LDAPConn *lc, LDAPURLDesc *srv, ber_socket_t sd ) +{ + struct timeval tv = { 0 }; + int rc; + + rc = ldap_int_poll( ld, sd, &tv ); + switch ( rc ) { + case 0: + /* now ready to start tls */ + lc->lconn_status = LDAP_CONNST_CONNECTED; + break; + + default: + rc = -1; + return rc; + case -2: + /* connect not completed yet */ + ld->ld_errno = LDAP_X_CONNECTING; + return rc; + } + +#ifdef HAVE_TLS + if ( ld->ld_options.ldo_tls_mode == LDAP_OPT_X_TLS_HARD || + !strcmp( srv->lud_scheme, "ldaps" )) { + + ++lc->lconn_refcnt; /* avoid premature free */ + + rc = ldap_int_tls_start( ld, lc, srv ); + + --lc->lconn_refcnt; + } +#endif + return rc; +} -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

RE: (ITS#6964) ./configure bug when specifying openssl as the TLS library to use
by the_uhu＠hotmail.com 09 Jun '11

09 Jun '11

--_845f4083-7211-40a8-bc3d-f1e94a6babb0_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I've just downloaded openldap stable fresh=2C opened up configure and this = is at line 19408 without an if check: LIBS=3D"-lssl -lcrypto -lRSAglue -lrsaref $LIBS" Also checked the source repository on the website and it's there also. Can you please double check? Paul. > Date: Wed=2C 8 Jun 2011 22:13:55 +0000 > From: openldap-its(a)OpenLDAP.org > To: the_uhu(a)hotmail.com > Subject: Re: (ITS#6964) ./configure bug when specifying openssl as the TL= S library to use >=20 > I don't know where your configure script came from=2C but there's nothing= related > to OpenSSL at line 19408 of the current released configure script=2C and = our > script has had logic to detect -lrsaref since 1999. >=20 > Closing this ITS. Use the actual configure script supplied by the OpenLDA= P > Project. = --_845f4083-7211-40a8-bc3d-f1e94a6babb0_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style></style> </head> <body class=3D'hmmessage'> I've just downloaded openldap stable fresh=2C opened up configure and this = is at line 19408 without an if check: LIBS=3D"-lssl -lcrypto -lRSAgl= ue -lrsaref $LIBS" Also checked the source repository on the website= and it's there also. Can you please double check? Paul. <= br> &gt=3B Date: Wed=2C 8 Jun 2011 22:13:55 +0000 &gt=3B From: openld= ap-its(a)OpenLDAP.org &gt=3B To: the_uhu(a)hotmail.com &gt=3B Subject: Re= : (ITS#6964) ./configure bug when specifying openssl as the TLS library to = use &gt=3B &gt=3B I don't know where your configure script came from= =2C but there's nothing related &gt=3B to OpenSSL at line 19408 of the c= urrent released configure script=2C and our &gt=3B script has had logic = to detect -lrsaref since 1999. &gt=3B &gt=3B Closing this ITS. Use t= he actual configure script supplied by the OpenLDAP &gt=3B Project. = </body> </html>= --_845f4083-7211-40a8-bc3d-f1e94a6babb0_--

1 0

Re: (ITS#6688) OpenLDAP 2.4.23 doesn't enforce ACLs on back-perl subordinate database
by quanah＠zimbra.com 09 Jun '11

09 Jun '11

--On Friday, October 29, 2010 4:35 PM +0000 mark.cave-ayland(a)siriusit.co.uk wrote: > Hi all, > > An update on this bug report: with a modified slapd.conf and a small > patch to the back-perl module, I can use the ACL mask to ensure that the > perl search function doesn't get invoked if disallowed by the ACLs. > > The patch works by creating a "fake" empty entry whose DN is the base of > the search, and then passing this entry into access_allowed() using code > borrowed from one of the other backends to either deny or allow access. > > http://pastebin.siriusit.co.uk/perlacl/slapd2.conf > http://pastebin.siriusit.co.uk/perlacl/openldap-backperl-acls.patch These are not accessible. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#6878) ppcache segfault with tavl_delete
by tjgates＠castlebranch.com 09 Jun '11

09 Jun '11

----- "Howard Chu" <hyc(a)symas.com> wrote: > Howard Chu wrote: > > Tyler Gates wrote: > >> After applying the patches for ITS #6848 and ITS #6898 I still get > crashes. > >> Here's the latest: > > ??? neither #6848 nor #6898 are relevant to pcache. I figured probably not but thought it may be important to know in terms as this is not just a straight 2.4.25 build... > > I think you should try the RE24 branch at this point, as a number of > other > pcache-related fixes have been merged there. Are you referring to OPENLDAP_REL_ENG_2_4 in the git tree? I'm not sure if I'll have the time (work) to tackle that but I'll see what I can do. > > > > Looks like a double-free. Can you reproduce this consistently? If > so, what are > > the steps? can you run slapd under valgrind and reproduce this? I can reproduce it consistently in terms that it crashes reliably after 2 to 4 days with 1 to 2 Linux hosts connected via pam-ldap account sessions. Other than that I've not been able to find a way to make it crash on demand. I do know it won't crash if it is run in the foreground with -d -1. I'm running it now under valgrind, any options you are looking for in particular? I'll report back the next time it crashes and/or I can try RE24. > >> > >> Program received signal SIGABRT, Aborted. > >> [Switching to Thread 0xae1edb70 (LWP 6121)] > >> 0xb76e2430 in __kernel_vsyscall () > >> (gdb) > >> (gdb) > >> (gdb) bt > >> #0 0xb76e2430 in __kernel_vsyscall () > >> #1 0xb71b4651 in *__GI_raise (sig=6) at > >> ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > >> #2 0xb71b7a82 in *__GI_abort () at abort.c:92 > >> #3 0xb71eb49d in __libc_message (do_abort=2, fmt=0xb72bff98 "*** > glibc > >> detected *** %s: %s: 0x%s ***\n") at > >> ../sysdeps/unix/sysv/linux/libc_fatal.c:189 > >> #4 0xb71f5591 in malloc_printerr (action=<value optimized out>, > str=0x6 > >> <Address 0x6 out of bounds>, ptr=0xb9584e80) at malloc.c:6266 > >> #5 0xb71f6de8 in _int_free (av=<value optimized out>, p=<value > >> optimized out>) at malloc.c:4794 > >> #6 0xb71f9ecd in *__GI___libc_free (mem=0xb9584e80) at > malloc.c:3738 > >> #7 0xb768ac20 in ber_memfree_x () from /usr/lib/liblber-2.4.so.2 > >> #8 0xb768acaf in ber_bvarray_free_x () from > /usr/lib/liblber-2.4.so.2 > >> #9 0xb768acf5 in ber_bvarray_free () from > /usr/lib/liblber-2.4.so.2 > >> #10 0xb7743e5d in attr_clean (a=0xb6dcc06c) at > >> /tmp/buildd/openldap-2.4.25/servers/slapd/attr.c:148 > >> #11 0xb7743efb in attrs_free (a=0xb6dcc06c) at > >> /tmp/buildd/openldap-2.4.25/servers/slapd/attr.c:198 > >> #12 0xb6d84b7f in hdb_cache_modify (bdb=0xb9536e10, e=0xb94f1dac, > >> newAttrs=0xb6dd6884, txn=0xb2176970, lock=0xae1ec930) at > cache.c:1238 > >> #13 0xb6d7008c in hdb_modify (op=0xae1eccfc, rs=0xae1ecad0) at > modify.c:662 > >> #14 0xb6d52e81 in remove_query_data (op=<value optimized out>, > >> query_uuid=<value optimized out>) > >> at > /tmp/buildd/openldap-2.4.25/servers/slapd/overlays/pcache.c:1829 > >> #15 0xb6d53d0b in consistency_check (ctx=0xae1ed1dc, > arg=0xb955e018) at > >> /tmp/buildd/openldap-2.4.25/servers/slapd/overlays/pcache.c:3520 > >> #16 0xb769d8b4 in ?? () from /usr/lib/libldap_r-2.4.so.2 > >> #17 0xb72e996e in start_thread (arg=0xae1edb70) at > pthread_create.c:300 > >> #18 0xb7257a4e in clone () at > ../sysdeps/unix/sysv/linux/i386/clone.S:130 > >> (gdb) continue > >> Continuing. > >> [Thread 0xaddecb70 (LWP 6122) exited] > >> [Thread 0xae1edb70 (LWP 6121) exited] > >> [Thread 0xae7f0b70 (LWP 6120) exited] > >> [Thread 0xaedf3b70 (LWP 6119) exited] > >> [Thread 0xaf2f5b70 (LWP 6118) exited] > >> [Thread 0xaf7f7b70 (LWP 6117) exited] > >> [Thread 0xafbf8b70 (LWP 6116) exited] > >> [Thread 0xafff9b70 (LWP 6115) exited] > >> [Thread 0xb04fbb70 (LWP 6114) exited] > >> [Thread 0xb08fcb70 (LWP 6113) exited] > >> [Thread 0xb582ab70 (LWP 5868) exited] > >> [Thread 0xb5320b70 (LWP 5869) exited] > >> [Thread 0xb4e1eb70 (LWP 5870) exited] > >> [Thread 0xb4a1db70 (LWP 5871) exited] > >> [Thread 0xb461cb70 (LWP 5872) exited] > >> [Thread 0xb421bb70 (LWP 5873) exited] > >> [Thread 0xb5c2bb70 (LWP 5867) exited] > >> > >> Program terminated with signal SIGABRT, Aborted. > >> The program no longer exists. > >> (gdb) > >> > >> > > > > > > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6964) ./configure bug when specifying openssl as the TLS library to use
by Howard Chu 09 Jun '11

09 Jun '11

I don't know where your configure script came from, but there's nothing related to OpenSSL at line 19408 of the current released configure script, and our script has had logic to detect -lrsaref since 1999. Closing this ITS. Use the actual configure script supplied by the OpenLDAP Project.

1 0

Re: (ITS#6878) ppcache segfault with tavl_delete
by hyc＠symas.com 08 Jun '11

08 Jun '11

Howard Chu wrote: > Tyler Gates wrote: >> After applying the patches for ITS #6848 and ITS #6898 I still get crashes. >> Here's the latest: ??? neither #6848 nor #6898 are relevant to pcache. I think you should try the RE24 branch at this point, as a number of other pcache-related fixes have been merged there. > > Looks like a double-free. Can you reproduce this consistently? If so, what are > the steps? can you run slapd under valgrind and reproduce this? >> >> Program received signal SIGABRT, Aborted. >> [Switching to Thread 0xae1edb70 (LWP 6121)] >> 0xb76e2430 in __kernel_vsyscall () >> (gdb) >> (gdb) >> (gdb) bt >> #0 0xb76e2430 in __kernel_vsyscall () >> #1 0xb71b4651 in *__GI_raise (sig=6) at >> ../nptl/sysdeps/unix/sysv/linux/raise.c:64 >> #2 0xb71b7a82 in *__GI_abort () at abort.c:92 >> #3 0xb71eb49d in __libc_message (do_abort=2, fmt=0xb72bff98 "*** glibc >> detected *** %s: %s: 0x%s ***\n") at >> ../sysdeps/unix/sysv/linux/libc_fatal.c:189 >> #4 0xb71f5591 in malloc_printerr (action=<value optimized out>, str=0x6 >> <Address 0x6 out of bounds>, ptr=0xb9584e80) at malloc.c:6266 >> #5 0xb71f6de8 in _int_free (av=<value optimized out>, p=<value >> optimized out>) at malloc.c:4794 >> #6 0xb71f9ecd in *__GI___libc_free (mem=0xb9584e80) at malloc.c:3738 >> #7 0xb768ac20 in ber_memfree_x () from /usr/lib/liblber-2.4.so.2 >> #8 0xb768acaf in ber_bvarray_free_x () from /usr/lib/liblber-2.4.so.2 >> #9 0xb768acf5 in ber_bvarray_free () from /usr/lib/liblber-2.4.so.2 >> #10 0xb7743e5d in attr_clean (a=0xb6dcc06c) at >> /tmp/buildd/openldap-2.4.25/servers/slapd/attr.c:148 >> #11 0xb7743efb in attrs_free (a=0xb6dcc06c) at >> /tmp/buildd/openldap-2.4.25/servers/slapd/attr.c:198 >> #12 0xb6d84b7f in hdb_cache_modify (bdb=0xb9536e10, e=0xb94f1dac, >> newAttrs=0xb6dd6884, txn=0xb2176970, lock=0xae1ec930) at cache.c:1238 >> #13 0xb6d7008c in hdb_modify (op=0xae1eccfc, rs=0xae1ecad0) at modify.c:662 >> #14 0xb6d52e81 in remove_query_data (op=<value optimized out>, >> query_uuid=<value optimized out>) >> at /tmp/buildd/openldap-2.4.25/servers/slapd/overlays/pcache.c:1829 >> #15 0xb6d53d0b in consistency_check (ctx=0xae1ed1dc, arg=0xb955e018) at >> /tmp/buildd/openldap-2.4.25/servers/slapd/overlays/pcache.c:3520 >> #16 0xb769d8b4 in ?? () from /usr/lib/libldap_r-2.4.so.2 >> #17 0xb72e996e in start_thread (arg=0xae1edb70) at pthread_create.c:300 >> #18 0xb7257a4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 >> (gdb) continue >> Continuing. >> [Thread 0xaddecb70 (LWP 6122) exited] >> [Thread 0xae1edb70 (LWP 6121) exited] >> [Thread 0xae7f0b70 (LWP 6120) exited] >> [Thread 0xaedf3b70 (LWP 6119) exited] >> [Thread 0xaf2f5b70 (LWP 6118) exited] >> [Thread 0xaf7f7b70 (LWP 6117) exited] >> [Thread 0xafbf8b70 (LWP 6116) exited] >> [Thread 0xafff9b70 (LWP 6115) exited] >> [Thread 0xb04fbb70 (LWP 6114) exited] >> [Thread 0xb08fcb70 (LWP 6113) exited] >> [Thread 0xb582ab70 (LWP 5868) exited] >> [Thread 0xb5320b70 (LWP 5869) exited] >> [Thread 0xb4e1eb70 (LWP 5870) exited] >> [Thread 0xb4a1db70 (LWP 5871) exited] >> [Thread 0xb461cb70 (LWP 5872) exited] >> [Thread 0xb421bb70 (LWP 5873) exited] >> [Thread 0xb5c2bb70 (LWP 5867) exited] >> >> Program terminated with signal SIGABRT, Aborted. >> The program no longer exists. >> (gdb) >> >> > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6899) Read Entry Control response value is not compliant to definition of SearchResultEntry
by masarati＠aero.polimi.it 08 Jun '11

08 Jun '11

> masarati(a)aero.polimi.it wrote: >>> With your patch the response control is now decoded correctly and it >>> behaves >>> as expected for all operations except Modify DN Operation: >>> It returns empty value lists for all attributes no matter how >>> deleteoldrdn >>> is >>> set. The DN returned is correct. >> >> I suspect ors_attrsonly is set by mistake. Please try this: >> >> + myop.ors_attrsonly = 0; > > With your last patch everything works as expected now. Thanks a lot. Great. I've committed it. Thanks, p.

1 0

Re: (ITS#6899) Read Entry Control response value is not compliant to definition of SearchResultEntry
by michael＠stroeder.com 08 Jun '11

08 Jun '11

masarati(a)aero.polimi.it wrote: >> With your patch the response control is now decoded correctly and it >> behaves >> as expected for all operations except Modify DN Operation: >> It returns empty value lists for all attributes no matter how deleteoldrdn >> is >> set. The DN returned is correct. > > I suspect ors_attrsonly is set by mistake. Please try this: > > + myop.ors_attrsonly = 0; With your last patch everything works as expected now. Thanks a lot. Ciao, Michael.

1 0

Re: (ITS#6899) Read Entry Control response value is not compliant to definition of SearchResultEntry
by masarati＠aero.polimi.it 08 Jun '11

08 Jun '11

> Pierangelo Masarati wrote: >> On 06/07/2011 12:58 PM, michael(a)stroeder.com wrote: >>> Any chance this will be fixed? >>> >>> It would be very handy for sync processes to get back the entryUUID >>> generated >>> by OpenLDAP of a new entry in an AddResponse without having to read the >>> new >>> entry once more. >> >> If I get things right, what seems to be missing is a >> LDAP_RES_SEARCH_ENTRY tag >> right before encoding the search entry, something like > > [..patch snipped..] > > Thanks! > > With your patch the response control is now decoded correctly and it > behaves > as expected for all operations except Modify DN Operation: > It returns empty value lists for all attributes no matter how deleteoldrdn > is > set. The DN returned is correct. > > Here's the trace log from the Python script: > > ----------------------------- snip ----------------------------- > *** ldap://localhost:2071/ - SimpleLDAPObject.rename > (('uid=ablume,ou=Users,ou=schulung,dc=stroeder,dc=local', 'uid=ablume2', > None, > 0, [('1.3.6.1.1.13.2', True, '0\x06\x04\x01*\x04\x01+')], None),{}) > => result: 5 > *** ldap://localhost:2071/ - SimpleLDAPObject.result4 ((5, 1, -1, 0, 0, > 0),{}) > => result: (109, [], 5, [('1.3.6.1.1.13.2', 0, > 'd\x82\x01N\x045uid=ablume2,ou=Users,ou=schulung,dc=stroeder,dc=local0\x82\x01\x130\x07\x04\x03uid1\x000\x0f\x04\x0bobjectClass1\x000\r\x04\tuidNumber1\x000\r\x04\tgidNumber1\x000\x11\x04\rhomeDirectory1\x000\x06\x04\x02cn1\x000\x19\x04\x15structuralObjectClass1\x000\r\x04\tentryUUID1\x000\x10\x04\x0ccreatorsName1\x000\x13\x04\x0fcreateTimestamp1\x000\x0c\x04\x08entryCSN1\x000\x11\x04\rmodifiersName1\x000\x13\x04\x0fmodifyTimestamp1\x000\x0b\x04\x07entryDN1\x000\x15\x04\x11subschemaSubentry1\x000\x13\x04\x0fhasSubordinates1\x00')]) > resp_ctrls[0].dn: uid=ablume2,ou=Users,ou=schulung,dc=stroeder,dc=local > resp_ctrls[0].entry: > {'cn': [], > 'createTimestamp': [], > 'creatorsName': [], > 'entryCSN': [], > 'entryDN': [], > 'entryUUID': [], > 'gidNumber': [], > 'hasSubordinates': [], > 'homeDirectory': [], > 'modifiersName': [], > 'modifyTimestamp': [], > 'objectClass': [], > 'structuralObjectClass': [], > 'subschemaSubentry': [], > 'uid': [], > 'uidNumber': []} > ----------------------------- snip ----------------------------- I suspect ors_attrsonly is set by mistake. Please try this: --- a/servers/slapd/result.c +++ b/servers/slapd/result.c @@ -1042,7 +1042,8 @@ slap_send_search_entry( Operation *op, SlapReply *rs ) #endif if ( op->o_res_ber ) { /* read back control */ - rc = ber_printf( ber, "{O{" /*}}*/, &rs->sr_entry->e_name ); + rc = ber_printf( ber, "t{O{" /*}}*/, + LDAP_RES_SEARCH_ENTRY, &rs->sr_entry->e_name ); } else { rc = ber_printf( ber, "{it{O{" /*}}}*/, op->o_msgid, LDAP_RES_SEARCH_ENTRY, &rs->sr_entry->e_name ); @@ -1744,6 +1745,7 @@ int slap_read_controls( myop.o_res_ber = ber; myop.o_callback = NULL; myop.ors_slimit = 1; + myop.ors_attrsonly = 0; rc = slap_send_search_entry( &myop, rs ); if( rc ) return rc;

1 0

Re: (ITS#6899) Read Entry Control response value is not compliant to definition of SearchResultEntry
by michael＠stroeder.com 08 Jun '11

08 Jun '11

Pierangelo Masarati wrote: > On 06/07/2011 12:58 PM, michael(a)stroeder.com wrote: >> Any chance this will be fixed? >> >> It would be very handy for sync processes to get back the entryUUID generated >> by OpenLDAP of a new entry in an AddResponse without having to read the new >> entry once more. > > If I get things right, what seems to be missing is a LDAP_RES_SEARCH_ENTRY tag > right before encoding the search entry, something like > [..patch snipped..] Thanks! With your patch the response control is now decoded correctly and it behaves as expected for all operations except Modify DN Operation: It returns empty value lists for all attributes no matter how deleteoldrdn is set. The DN returned is correct. Here's the trace log from the Python script: ----------------------------- snip ----------------------------- *** ldap://localhost:2071/ - SimpleLDAPObject.rename (('uid=ablume,ou=Users,ou=schulung,dc=stroeder,dc=local', 'uid=ablume2', None, 0, [('1.3.6.1.1.13.2', True, '0\x06\x04\x01*\x04\x01+')], None),{}) => result: 5 *** ldap://localhost:2071/ - SimpleLDAPObject.result4 ((5, 1, -1, 0, 0, 0),{}) => result: (109, [], 5, [('1.3.6.1.1.13.2', 0, 'd\x82\x01N\x045uid=ablume2,ou=Users,ou=schulung,dc=stroeder,dc=local0\x82\x01\x130\x07\x04\x03uid1\x000\x0f\x04\x0bobjectClass1\x000\r\x04\tuidNumber1\x000\r\x04\tgidNumber1\x000\x11\x04\rhomeDirectory1\x000\x06\x04\x02cn1\x000\x19\x04\x15structuralObjectClass1\x000\r\x04\tentryUUID1\x000\x10\x04\x0ccreatorsName1\x000\x13\x04\x0fcreateTimestamp1\x000\x0c\x04\x08entryCSN1\x000\x11\x04\rmodifiersName1\x000\x13\x04\x0fmodifyTimestamp1\x000\x0b\x04\x07entryDN1\x000\x15\x04\x11subschemaSubentry1\x000\x13\x04\x0fhasSubordinates1\x00')]) resp_ctrls[0].dn: uid=ablume2,ou=Users,ou=schulung,dc=stroeder,dc=local resp_ctrls[0].entry: {'cn': [], 'createTimestamp': [], 'creatorsName': [], 'entryCSN': [], 'entryDN': [], 'entryUUID': [], 'gidNumber': [], 'hasSubordinates': [], 'homeDirectory': [], 'modifiersName': [], 'modifyTimestamp': [], 'objectClass': [], 'structuralObjectClass': [], 'subschemaSubentry': [], 'uid': [], 'uidNumber': []} ----------------------------- snip ----------------------------- Ciao, Michael.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs