- openldap-bugs - openldap.org

(ITS#4890) Enhancement: Default Values overlay (patch)
by docelic＠mail.inet.hr 22 Mar '07

22 Mar '07

Full_Name: Davor Ocelic Version: CVS-HEAD OS: Linux URL: http://www.hcoop.net/~docelic/openldap-slapd.overlays.defvals.patch Submission from: (NULL) (213.147.110.16) Hello, Attached is a patch which adds a "Default Attribute Values" functionality to OpenLDAP. It is implemented as an overlay named "defvals", and the patch is done against cvs-head of today. Complete documentation is included in the slapo-defvals(5) manual page. The overlay code itself is commented as well, as a help for others writing overlays. Feel free to trim comments or improve code as you see fit. Davor Ocelic

1 0

Re: (ITS#4888) Enhance back-sql with paged results
by adamson＠andrew.cmu.edu 22 Mar '07

22 Mar '07

Hi Pierangelo > Let me note that the patch doesn't build fine (you need to declare in > advance the static functions you're only defining at the end), and it > seems to work incorrectly. By running the simple sql-test000 with mysql > (which fails because now the order has changed; my fault: should have > added -S "" to searches), if I search without the control, I correctly > get 6 entries and a referral; if I search with paged results and a page > size less than 6, I only get 5 entries. The root entry is missing, but > I have no idea of the reason, I couldn't infer anything from the code or > the logs. Can you check? When I checked on the patch file in my Emacs window this morning I saw the "modified buffer" flag was still on because I hadn't saved the final version. Grrrr. It included the function declarations and one last fix. Sorry about that. When I extract the last ID number from the cookie, I have to make sure we're in the same objectClass as when the ID number was saved. I've replaced the patch file on my web server. If it doesn't fix the root entry bug you're seeing, could you show me the search you're performing? I'll have to more closely follow what's happening in the switch ( bsi.bsi_scope ) { segment around line 2115 in backsql_search() to see if there is some special case for the root entry. -Mark Adamson Carnegie Mellon

1 0

(ITS#4889) Tranlucent Overlay
by ghenry＠suretecsystems.com 22 Mar '07

22 Mar '07

Full_Name: Gavin Henry Version: 2.3.34 OS: FC6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (80.229.93.1) Dear All, Just been playing iwth slapo-translucent, and ldapmodified an entry on the remote side successfully. However, when I search for that entry, after the first or second search, slapd aborts. I merely changed a birthday and title for my own ghenry entry Here my slapd.conf: ------------------------- include /usr/local/etc/openldap/schema/core.schema pidfile /usr/local/var/run/slapd.pid argsfile /usr/local/var/run/slapd.args # Load dynamic backend modules: modulepath /usr/local/libexec/openldap moduleload back_bdb.la moduleload back_ldap.la moduleload translucent.la moduleload rwm.la database bdb directory /usr/local/var/openldap-data cachesize 10000 suffix "dc=suretecsystems,dc=com" rootdn "cn=manager,dc=suretecsystems,dc=com" rootpw secret index default eq index objectClass,uid,dc,o,ou overlay translucent overlay rwm uri ldap://192.168.10.103:389 lastmod off idassert-bind binddn="cn=manager,dc=suretecsystems,dc=com" credentials=secret rwm-map objectclass * * rwm-map attribute * * ------------------------- Using db-4.2.52 and the 5 patches. He's a gdb session: [Thread debugging using libthread_db enabled] [New Thread -1209051456 (LWP 4529)] @(#) $OpenLDAP: slapd 2.3.34 (Mar 20 2007 14:53:32) $ ghenry@suretec:/home/ghenry/openldap/openldap-2.3.34/servers/slapd WARNING: No dynamic config support for database bdb. WARNING: No dynamic config support for overlay rwm. WARNING: No dynamic config support for overlay translucent. bdb_db_open: unclean shutdown detected; attempting recovery. slapd starting [New Thread -1547441264 (LWP 4532)] conn=0 fd=15 ACCEPT from IP=127.0.0.1:33269 (IP=0.0.0.0:389) [New Thread -1557931120 (LWP 4534)] conn=0 op=0 BIND dn="" method=128 conn=0 op=0 RESULT tag=97 err=0 text= [New Thread -1569473648 (LWP 4535)] conn=0 op=1 SRCH base="dc=suretecsystems,dc=com" scope=2 deref=0 filter="(uid=ghenry)" request done: ld 0x8e0dd10 msgid 1 request done: ld 0x8e0dd10 msgid 2 conn=0 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text= conn=0 op=2 UNBIND conn=0 fd=15 closed *** glibc detected *** /usr/local/libexec/slapd: corrupted double-linked list: 0x08e19458 *** ======= Backtrace: ========= /lib/libc.so.6[0xb0448b] /lib/libc.so.6[0xb066f3] /lib/libc.so.6(__libc_calloc+0x8d)[0xb07bdd] /lib/libc.so.6(open_memstream+0x5d)[0xafce7d] /lib/libc.so.6(__vsyslog_chk+0x76)[0xb69656] /lib/libc.so.6(syslog+0x2a)[0xb69bfa] /usr/local/libexec/slapd[0x80687e5] /usr/local/libexec/slapd[0x8068c9c] /usr/local/lib/libldap_r-2.3.so.0[0x11b56d] /lib/libpthread.so.0[0xc133db] /lib/libc.so.6(clone+0x5e)[0xb6d26e] ======= Memory map: ======== 00110000-00148000 r-xp 00000000 fd:00 10953537 /usr/local/lib/libldap_r-2.3.so.0.2.22 00148000-0014a000 rwxp 00037000 fd:00 10953537 /usr/local/lib/libldap_r-2.3.so.0.2.22 0014a000-0014f000 rwxp 0014a000 00:00 0 0014f000-0015a000 r-xp 00000000 fd:00 10953351 /usr/local/lib/liblber-2.3.so.0.2.22 0015a000-0015b000 rwxp 0000a000 fd:00 10953351 /usr/local/lib/liblber-2.3.so.0.2.22 0015b000-0015f000 r-xp 00000000 fd:00 11025778 /usr/lib/sasl2/libcrammd5.so.2.0.22 0015f000-00160000 rwxp 00003000 fd:00 11025778 /usr/lib/sasl2/libcrammd5.so.2.0.22 00160000-0023b000 r-xp 00000000 fd:00 11031861 /usr/lib/sasl2/libsasldb.so.2.0.22 0023b000-0023d000 rwxp 000db000 fd:00 11031861 /usr/lib/sasl2/libsasldb.so.2.0.22 0023d000-00251000 r-xp 00000000 fd:00 820357 /usr/local/libexec/openldap/back_ldap-2.3.so.0.2.22 00251000-00253000 rwxp 00013000 fd:00 820357 /usr/local/libexec/openldap/back_ldap-2.3.so.0.2.22 00253000-0025e000 r-xp 00000000 fd:00 2290131 /lib/libgcc_s-4.1.1-20070105.so.1 0025e000-0025f000 rwxp 0000a000 fd:00 2290131 /lib/libgcc_s-4.1.1-20070105.so.1 0027c000-00282000 r-xp 00000000 fd:00 10928729 /usr/lib/libltdl.so.3.1.4 00282000-00283000 rwxp 00005000 fd:00 10928729 /usr/lib/libltdl.so.3.1.4 002e2000-002e9000 r-xp 00000000 fd:00 10929498 /usr/lib/libwrap.so.0.7.6 002e9000-002ea000 rwxp 00007000 fd:00 10929498 /usr/lib/libwrap.so.0.7.6 002ea000-003a5000 r-xp 00000000 fd:00 393521 /usr/local/BerkeleyDB.4.2/lib/libdb-4.2.so 003a5000-003a7000 rwxp 000bb000 fd:00 393521 /usr/local/BerkeleyDB.4.2/lib/libdb-4.2.so 003f3000-003fc000 r-xp 00000000 fd:00 2289320 /lib/libnss_files-2.5.so 003fc000-003fd000 r-xp 00008000 fd:00 2289320 /lib/libnss_files-2.5.so 003fd000-003fe000 rwxp 00009000 fd:00 2289320 /lib/libnss_files-2.5.so 004ca000-004ce000 r-xp 00000000 fd:00 11028143 /usr/lib/sasl2/liblogin.so.2.0.22 004ce000-004cf000 rwxp 00003000 fd:00 11028143 /usr/lib/sasl2/liblogin.so.2.0.22 00504000-00528000 r-xp 00000000 fd:00 820345 /usr/local/libexec/openldap/back_bdb-2.3.so.0.2.22 00528000-00529000 rwxp 00024000 fd:00 820345 /usr/local/libexec/openldap/back_bdb-2.3.so.0.2.22 00529000-00535000 rwxp 00529000 00:00 0 00695000-00696000 r-xp 00695000 00:00 0 [vdso] 0071d000-00721000 r-xp 00000000 fd:00 820437 /usr/local/libexec/openldap/translucent-2.3.so.0.2.22 00721000-00722000 rwxp 00003000 fd:00 820437 /usr/local/libexec/openldap/translucent-2.3.so.0.2.22 007fe000-00809000 r-xp 00000000 fd:00 11025782 /usr/lib/sasl2/libdigestmd5.so.2.0.22 00809000-0080a000 rwxp 0000b000 fd:00 11025782 /usr/lib/sasl2/libdigestmd5.so.2.0.22 00916000-00929000 r-xp 00000000 fd:00 2290139 /lib/libnsl-2.5.so 00929000-0092a000 r-xp 00012000 fd:00 2290139 /lib/libnsl-2.5.so 0092a000-0092b000 rwxp 00013000 fd:00 2290139 /lib/libnsl-2.5.so 0092b000-0092d000 rwxp 0092b000 00:00 0 0092f000-0093e000 r-xp 00000000 fd:00 2290132 /lib/libresolv-2.5.so 0093e000-0093f000 r-xp 0000e000 fd:00 2290132 /lib/libresolv-2.5.so 0093f000-00940000 rwxp 0000f000 fd:00 2290132 /lib/libresolv-2.5.so 00940000-00942000 rwxp 00940000 00:00 0 0099a000-0099e000 r-xp 00000000 fd:00 11021253 /usr/lib/sasl2/libanonymous.so.2.0.22 0099e000-0099f000 rwxp 00003000 fd:00 11021253 /usr/lib/sasl2/libanonymous.so.2.0.22 009a5000-009a7000 r-xp 00000000 fd:00 2290133 /lib/libcom_err.so.2.1 009a7000-009a8000 rwxp 00001000 fd:00 2290133 /lib/libcom_err.so.2.1 009aa000-00a2e000 r-xp 00000000 fd:00 10928447 /usr/lib/libkrb5.so.3.2 00a2e000-00a30000 rwxp 00084000 fd:00 10928447 /usr/lib/libkrb5.so.3.2 00a32000-00a39000 r-xp 00000000 fd:00 10928445 /usr/lib/libkrb5support.so.0.1 00a39000-00a3a000 rwxp 00006000 fd:00 10928445 /usr/lib/libkrb5support.so.0.1 00a3c000-00a61000 r-xp 00000000 fd:00 10928446 /usr/lib/libk5crypto.so.3.0 00a61000-00a62000 rwxp 00025000 fd:00 10928446 /usr/lib/libk5crypto.so.3.0 00a83000-00a9c000 r-xp 00000000 fd:00 2289282 /lib/ld-2.5.so 00a9c000-00a9d000 r-xp 00018000 fd:00 2289282 /lib/ld-2.5.so 00a9d000-00a9e000 rwxp 00019000 fd:00 2289282 /lib/ld-2.5.so 00aa0000-00bd7000 r-xp 00000000 fd:00 2289319 /lib/libc-2.5.so 00bd7000-00bd9000 r-xp 00137000 fd:00 2289319 /lib/libc-2.5.so 00bd9000-00bda000 rwxp 00139000 fd:00 2289319 /lib/libc-2.5.so 00bda000-00bdd000 rwxp 00bda000 00:00 0 00c08000-00c0a000 r-xp 00000000 fd:00 2289374 /lib/libdl-2.5.so 00c0a000-00c0b000 r-xp 00001000 fd:00 2289374 /lib/libdl-2.5.so 00c0b000-00c0c000 rwxp 00002000 fd:00 2289374 /lib/libdl-2.5.so 00c0e000-00c21000 r-xp 00000000 fd:00 2289321 /lib/libpthread-2.5.so 00c21000-00c22000 r-xp 00012000 fd:00 2289321 /lib/libpthread-2.5.so 00c22000-00c23000 rwxp 00013000 fd:00 2289321 /lib/libpthread-2.5.so 00c23000-00c25000 rwxp 00c23000 00:00 0 00c27000-00c39000 r-xp 00000000 fd:00 10928409 /usr/lib/libz.so.1.2.3 00c39000-00c3a000 rwxp 00011000 fd:00 10928409 /usr/lib/libz.so.1.2.3 00c49000-00c51000 r-xp 00000000 fd:00 820429 /usr/local/libexec/openldap/rwm-2.3.so.0.2.22 00c51000-00c52000 rwxp 00008000 fd:00 820429 /usr/local/libexec/openldap/rwm-2.3.so.0.2.22 00da4000-00da8000 r-xp 00000000 fd:00 11028147 /usr/lib/sasl2/libplain.so.2.0.22 00da8000-00da9000 rwxp 00003000 fd:00 11028147 /usr/lib/sasl2/libplain.so.2.0.22 06574000-06690000 r-xp 00000000 fd:00 2290134 /lib/libcrypto.so.0.9.8b 06690000-066a2000 rwxp 0011c000 fd:00 2290134 /lib/libcrypto.so.0.9.8b 066a2000-066a6000 rwxp 066a2000 00:00 0 066a8000-066d2000 r-xp 00000000 fd:00 10928450 /usr/lib/libgssapi_krb5.so.2.2 066d2000-066d3000 rwxp 00029000 fd:00 10928450 /usr/lib/libgssapi_krb5.so.2.2 066d5000-06716000 r-xp 00000000 fd:00 2290135 /lib/libssl.so.0.9.8b 06716000-0671a000 rwxp 00040000 fd:00 2290135 /lib/libssl.so.0.9.8b 06aeb000-06af0000 r-xp 00000000 fd:00 2290136 /lib/libcrypt-2.5.so 06af0000-06af1000 r-xp 00004000 fd:00 2290136 /lib/libcrypt-2.5.so 06af1000-06af2000 rwxp 00005000 fd:00 2290136 /lib/libcrypt-2.5.so 06af2000-06b19000 rwxp 06af2000 00:00 0 06dcb000-06de3000 r-xp 00000000 fd:00 10928451 /usr/lib/libsasl2.so.2.0.22 06de3000-06de4000 rwxp 00017000 fd:00 10928451 /usr/lib/libsasl2.so.2.0.22 08048000-0811d000 r-xp 00000000 fd:00 10953555 /usr/local/libexec/slapd 0811d000-08121000 rw-p 000d4000 fd:00 10953555 /usr/local/libexec/slapd 08121000-08124000 rw-p 08121000 00:00 0 08d12000-08e2d000 rw-p 08d12000 00:00 0 a1b00000-a1b21000 rw-p a1b00000 00:00 0 a1b21000-a1c00000 ---p a1b21000 00:00 0 a1c3a000-a1d3b000 rw-p a1c3a000 00:00 0 a1d3b000-a1d3c000 ---p a1d3b000 00:00 0 a1d3c000-a283d000 rw-p a1d3c000 00:00 0 a283d000-a283e000 ---p a283d000 00:00 0 a283e000-a323e000 rw-p a283e000 00:00 0 a323e000-a323f000 ---p a323e000 00:00 0 a323f000-a3c3f000 rw-p a323f000 00:00 0 a3c3f000-a3c45000 rw-s 00000000 fd:00 821479 /usr/local/var/openldap-data/__db.005 a3c45000-a3cb3000 rw-s 00000000 fd:00 821478 /usr/local/var/openldap-data/__db.004 a3cb3000-a3ef3000 rw-s 00000000 fd:00 821477 /usr/local/var/openldap-data/__db.003 a3ef3000-b7ef5000 rw-s 00000000 fd:00 820670 /usr/local/var/openldap-data/__db.002 b7ef5000-b7efa000 rw-p b7ef5000 00:00 0 b7f0e000-b7f12000 rw-s 00000000 fd:00 820669 /usr/local/var/openldap-data/__db.001 b7f12000-b7f13000 rw-p b7f12000 00:00 0 bfe20000-bfe36000 rw-p bfe20000 00:00 0 [stack] Program received signal SIGABRT, Aborted. [Switching to Thread -1569473648 (LWP 4535)] 0x00695402 in __kernel_vsyscall () (gdb) bt #0 0x00695402 in __kernel_vsyscall () #1 0x00ac8d40 in raise () from /lib/libc.so.6 #2 0x00aca591 in abort () from /lib/libc.so.6 #3 0x00afe33b in __libc_message () from /lib/libc.so.6 #4 0x00b0448b in malloc_consolidate () from /lib/libc.so.6 #5 0x00b066f3 in _int_malloc () from /lib/libc.so.6 #6 0x00b07bdd in calloc () from /lib/libc.so.6 #7 0x00afce7d in open_memstream () from /lib/libc.so.6 #8 0x00b69656 in __vsyslog_chk () from /lib/libc.so.6 #9 0x00b69bfa in syslog () from /lib/libc.so.6 #10 0x080687e5 in connection2anonymous () #11 0x08068c9c in connection2anonymous () #12 0x0011b56d in ldap_int_thread_pool_wrapper (xpool=0x0) at tpool.c:478 #13 0x00c133db in start_thread () from /lib/libpthread.so.0 #14 0x00b6d26e in clone () from /lib/libc.so.6 Please let me know what else is needed. Thanks, Gavin. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

1 0

RE: (ITS#4886) slapd stopping with no error message
by douglas＠gpc.edu 22 Mar '07

22 Mar '07

Thanks for the quick reply. I will try to get some things together in one or more emails. I got the following: "Bis Dienstag, den 2. April bin ich leider nicht erreichbar. Sollte Ihr Anliegen nicht so lange warten können, wenden Sie sich bitte an unsere Hotline unter der Rufnummer 0511-5181188. --------------------------------------------------------------------- Mit freundlichen Grüßen Johannes Königsmann Gutenberg Rechenzentrum GmbH & Co. KG System-Management August-Madsack-Straße 1 30559 Hannover Tel. : +49 511 518-1107 Fax : +49 511 518-1102 e-Mail: koenigsmann(a)gutenberg-rz.de Internet: www.gutenberg-rz.de _________________________________________ Gutenberg Rechenzentrum GmbH & Co. KG Sitz: Hannover Handelsregister: Hannover HRA 21 669 Geschäftsführer: Karl-Rüdiger Garbs, Dr. Claudia Hümpel" I wanted to reply to him letting him know that I did know German (wish I did), but I was a little hesitant this might not be a legitimate response to my its. Is there a way I could find out if he is legitimate or if he is not, then I would ignore it. Thanks for any help with this side question. Thanks! -----Original Message----- From: Howard Chu [mailto:hyc@symas.com] Sent: Thursday, March 22, 2007 4:36 AM To: douglas(a)gpc.edu Cc: Kurt Zeilenga Subject: Re: (ITS#4886) slapd stopping with no error message Also show the output for print *ber at the crash location Seems like something is bad in your build environment if you can get it to crash after only one search. Have you run the test suite successfully? douglas(a)gpc.edu wrote: > Full_Name: Douglas Jones > Version: 2.3.34 > OS: RHEL4 (linux) > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (168.28.202.22) > > > Without efence, after the server has been runing between 3 and 15 days, > it varies, the sever just stops. Even using ulimit on core size, I did > not have luck getting a core file. Per recomendation of the newgroups, > I used efence and it crashed on the first lookup. I got the following under > gdb: > > (previous -d 1 output cut) > It did return the names to my client, which was good, but just crashed after > (during) that. Please let me know if I can do anythin else. Thanks! -- -- Howard Chu Chief Architect, 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#4888) Enhance back-sql with paged results
by ando＠sys-net.it 22 Mar '07

22 Mar '07

hyc(a)symas.com wrote: > adamson(a)cmu.edu wrote: >> Full_Name: Mark Adamson >> Version: HEAD >> OS: Solaris 2.8 >> URL: http://null.andrew.cmu.edu/openldap/sql_paged_results.patch >> Submission from: (NULL) (128.2.234.24) >> >> >> Here at Carnegie Mellon we had a need to use the LDAP_CONTROL_PAGEDRESULTS >> control with the SQL backend. The patch to add this is not hard, and was mostly >> copied from the back-bdb/search.c file. >> >> http://null.andrew.cmu.edu/openldap/sql_paged_results.patch >> >> The only challenge was the contents of the cookie that is used to maintain >> state. The slap.h file defines the PagedResultsCookie type to be an unsigned >> long, so I wanted to fit everything into that. The design idea was to keep the >> ldap_entries.id value of the last returned entry in the cookie so that >> subsequent searches could add a "AND ldap_entries.id > COOKIEVALUE" clause to >> the SQL query. However, the gathering of candidate entries is done across all >> objectClasses with avl_apply(), so if one OC returns an entry with a high >> ldap_entries.id, objectClasses that come later in the AVL could miss entries. >> For this reason, I add the oc_map_id of the last returned entry to the cookie, >> and I adjusted the avl_apply() call to run through the objectClasses in numeric >> order. In this way, when subsequent pages of entries are requested, all of the >> objectClasses that were completed by previous pages can be skipped for the new >> page. When we get to the objectClass where the previous page left off, we take >> the ldap_entries.id from the cookie and apply the above mentioned SQL clause. > > A more appropriate change would probably be to change the cookie type to > a berval so that arbitrary data may be used as needed by each backend. > Then you can set both the oc_map_id and the ldap_entries.id. > > Ultimately this sort of thing should be handled almost entirely by the > frontend, with just a single call in the backend to fill a cookie struct > for the current search state. I concur (was about to suggest the same: move parse_paged_cookie() and send_paged_response() to servers/slapd/result.c, adding as much as required to customize it from within the backend specific call. Let me note that the patch doesn't build fine (you need to declare in advance the static functions you're only defining at the end), and it seems to work incorrectly. By running the simple sql-test000 with mysql (which fails because now the order has changed; my fault: should have added -S "" to searches), if I search without the control, I correctly get 6 entries and a referral; if I search with paged results and a page size less than 6, I only get 5 entries. The root entry is missing, but I have no idea of the reason, I couldn't infer anything from the code or the logs. Can you check? p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

Re: (ITS#4886) slapd stopping with no error message
by hyc＠symas.com 22 Mar '07

22 Mar '07

Also show the output for print *ber at the crash location Seems like something is bad in your build environment if you can get it to crash after only one search. Have you run the test suite successfully? douglas(a)gpc.edu wrote: > Full_Name: Douglas Jones > Version: 2.3.34 > OS: RHEL4 (linux) > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (168.28.202.22) > > > Without efence, after the server has been runing between 3 and 15 days, > it varies, the sever just stops. Even using ulimit on core size, I did > not have luck getting a core file. Per recomendation of the newgroups, > I used efence and it crashed on the first lookup. I got the following under > gdb: > > (previous -d 1 output cut) > It did return the names to my client, which was good, but just crashed after > (during) that. Please let me know if I can do anythin else. Thanks! -- -- Howard Chu Chief Architect, 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#4888) Enhance back-sql with paged results
by hyc＠symas.com 22 Mar '07

22 Mar '07

adamson(a)cmu.edu wrote: > Full_Name: Mark Adamson > Version: HEAD > OS: Solaris 2.8 > URL: http://null.andrew.cmu.edu/openldap/sql_paged_results.patch > Submission from: (NULL) (128.2.234.24) > > > Here at Carnegie Mellon we had a need to use the LDAP_CONTROL_PAGEDRESULTS > control with the SQL backend. The patch to add this is not hard, and was mostly > copied from the back-bdb/search.c file. > > http://null.andrew.cmu.edu/openldap/sql_paged_results.patch > > The only challenge was the contents of the cookie that is used to maintain > state. The slap.h file defines the PagedResultsCookie type to be an unsigned > long, so I wanted to fit everything into that. The design idea was to keep the > ldap_entries.id value of the last returned entry in the cookie so that > subsequent searches could add a "AND ldap_entries.id > COOKIEVALUE" clause to > the SQL query. However, the gathering of candidate entries is done across all > objectClasses with avl_apply(), so if one OC returns an entry with a high > ldap_entries.id, objectClasses that come later in the AVL could miss entries. > For this reason, I add the oc_map_id of the last returned entry to the cookie, > and I adjusted the avl_apply() call to run through the objectClasses in numeric > order. In this way, when subsequent pages of entries are requested, all of the > objectClasses that were completed by previous pages can be skipped for the new > page. When we get to the objectClass where the previous page left off, we take > the ldap_entries.id from the cookie and apply the above mentioned SQL clause. A more appropriate change would probably be to change the cookie type to a berval so that arbitrary data may be used as needed by each backend. Then you can set both the oc_map_id and the ldap_entries.id. Ultimately this sort of thing should be handled almost entirely by the frontend, with just a single call in the backend to fill a cookie struct for the current search state. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#4888) Enhance back-sql with paged results
by adamson＠cmu.edu 21 Mar '07

21 Mar '07

Full_Name: Mark Adamson Version: HEAD OS: Solaris 2.8 URL: http://null.andrew.cmu.edu/openldap/sql_paged_results.patch Submission from: (NULL) (128.2.234.24) Here at Carnegie Mellon we had a need to use the LDAP_CONTROL_PAGEDRESULTS control with the SQL backend. The patch to add this is not hard, and was mostly copied from the back-bdb/search.c file. http://null.andrew.cmu.edu/openldap/sql_paged_results.patch The only challenge was the contents of the cookie that is used to maintain state. The slap.h file defines the PagedResultsCookie type to be an unsigned long, so I wanted to fit everything into that. The design idea was to keep the ldap_entries.id value of the last returned entry in the cookie so that subsequent searches could add a "AND ldap_entries.id > COOKIEVALUE" clause to the SQL query. However, the gathering of candidate entries is done across all objectClasses with avl_apply(), so if one OC returns an entry with a high ldap_entries.id, objectClasses that come later in the AVL could miss entries. For this reason, I add the oc_map_id of the last returned entry to the cookie, and I adjusted the avl_apply() call to run through the objectClasses in numeric order. In this way, when subsequent pages of entries are requested, all of the objectClasses that were completed by previous pages can be skipped for the new page. When we get to the objectClass where the previous page left off, we take the ldap_entries.id from the cookie and apply the above mentioned SQL clause. To fit both the oc_map_id and ldap_entries.id into a 32bit cookie, I had to make a sacrifice. I took 6 bits and used them for oc_map_id and the remaining 26 bits for ldap_entries.id. This means max(oc_map_id) needs to be < 64 and max(ldap_entries.id) needs to be < 134,217,728. If the PagedResultsCookie type is ever expanded to be a berval, we can store both oc_map_id and ldap_entries.id in their full glory. Anyway, try it out. It's a quick patch. -Mark Adamson Carnegie Mellon University

1 0

(ITS#4887) JLDAP - com.novell.sasl.client.DigestMD5SaslClient and RFC2831
by giovannix＠gmail.com 21 Mar '07

21 Mar '07

Full_Name: Giovanni Almeida Santos Version: 2.3.34 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (200.199.204.60) According to RFC2831 (Using Digest Authentication as a SASL Mechanism), the rules for a "digest-response" is defined as follows: digest-response = 1#( username | realm | nonce | cnonce | nonce-count | qop | digest-uri | response | maxbuf | charset | cipher | authzid | auth-param ) username = "username" "=" <"> username-value <"> username-value = qdstr-val ... authzid = "authzid" "=" <"> authzid-value <"> authzid-value = qdstr-val com.novell.sasl.client.DigestMD5SaslClient class does not implement that RFC at all because it does not use authzid as described above. To correct this, it is necessary modify two methods on DigestMD5SaslClient: DigestCalcHA1 and createDigestResponse. In the DigestCalcHA1 method it is necessary include the code delimited by // -->> as follows: char[] DigestCalcHA1( String algorithm, String userName, String realm, String password, String nonce, String clientNonce) throws SaslException { ... if ("md5-sess".equals(algorithm)) { md.update(hash); md.update(":".getBytes("UTF-8")); md.update(nonce.getBytes("UTF-8")); md.update(":".getBytes("UTF-8")); md.update(clientNonce.getBytes("UTF-8")); // -->> It is necessary to allow Proxy Authorization if(m_authorizationId != null && !"".equals(m_authorizationId)) { md.update(":".getBytes("UTF-8")); md.update(m_authorizationId.getBytes("UTF-8")); } // -->> End hash = md.digest(); } ... } In the createDigestResponse method it is necessary remove <code>digestResponse.append(m_authorizationId)<code> (commented below) and insert the code delimited by // -->> private String createDigestResponse( byte[] challenge) throws SaslException { ... digestResponse.append("username=\""); //digestResponse.append(m_authorizationId); // -->> It is necessary to allow Proxy Authorization digestResponse.append(m_name); if(m_authorizationId != null && !"".equals(m_authorizationId)) { digestResponse.append("\",authzid=\""); digestResponse.append(m_authorizationId); } // -->> End ... } Without these modifications, proxy authorization is not possible.

1 0

(ITS#4886) slapd stopping with no error message
by douglas＠gpc.edu 21 Mar '07

21 Mar '07

Full_Name: Douglas Jones Version: 2.3.34 OS: RHEL4 (linux) URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (168.28.202.22) Without efence, after the server has been runing between 3 and 15 days, it varies, the sever just stops. Even using ulimit on core size, I did not have luck getting a core file. Per recomendation of the newgroups, I used efence and it crashed on the first lookup. I got the following under gdb: (previous -d 1 output cut) >>> dnPrettyNormal: <cn=Write,cn=Waiters,cn=Monitor> <<< dnPrettyNormal: <cn=Write,cn=Waiters,cn=Monitor>, <cn=write,cn=waiters,cn=monitor> >>> dnNormalize: <> <<< dnNormalize: <> >>> dnNormalize: <> <<< dnNormalize: <> <= str2entry(cn=Write,cn=Waiters,cn=Monitor) -> 0x260d9fd8 backend_startup_one: starting "o=gpc,c=us" slapd starting [New Thread 635861936 (LWP 10061)] [New Thread 631663536 (LWP 10062)] [New Thread 627465136 (LWP 10063)] [New Thread 623266736 (LWP 10064)] [New Thread 619068336 (LWP 10065)] >>> slap_listener(ldap://:389/) connection_get(33): got connid=0 connection_read(33): checking for input on id=0 ber_get_next ber_get_next: tag 0x30 len 16 contents: ber_get_next do_bind ber_scanf fmt ({imt) ber: ber_scanf fmt (m}) ber: >>> dnPrettyNormal: <> <<< dnPrettyNormal: <>, <> do_bind: version=3 dn="" method=128 send_ldap_result: conn=0 op=0 p=3 send_ldap_response: msgid=30 tag=97 err=0 ber_flush: 14 bytes to sd 33 connection_get(33): got connid=0 connection_read(33): checking for input on id=0 ber_get_next Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 635861936 (LWP 10061)] ber_get_next (sb=0x25f2ffe8, len=0x25e6427c, ber=0x25f65fd4) at io.c:551 551 if (*ber->ber_ptr & 0x80) { /* multi-byte */ (gdb) bt full #0 ber_get_next (sb=0x25f2ffe8, len=0x25e6427c, ber=0x25f65fd4) at io.c:551 l = Variable "l" is not available. (gdb) thread apply all bt Thread 6 (Thread 619068336 (LWP 10065)): #0 0x0028e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x004e7b26 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 #2 0x0812d25b in ldap_int_thread_pool_wrapper (xpool=0xb725df58) at tpool.c:490 #3 0x004e5371 in start_thread () from /lib/tls/libpthread.so.0 #4 0x0036effe in clone () from /lib/tls/libc.so.6 Thread 5 (Thread 623266736 (LWP 10064)): #0 0x0028e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x004e7b26 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 #2 0x0812d25b in ldap_int_thread_pool_wrapper (xpool=0xb725df58) at tpool.c:490 #3 0x004e5371 in start_thread () from /lib/tls/libpthread.so.0 #4 0x0036effe in clone () from /lib/tls/libc.so.6 Thread 4 (Thread 627465136 (LWP 10063)): #0 0x0028e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x004e7b26 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0 ---Type <return> to continue, or q <return> to quit--- #2 0x0812d25b in ldap_int_thread_pool_wrapper (xpool=0xb725df58) at tpool.c:490 #3 0x004e5371 in start_thread () from /lib/tls/libpthread.so.0 #4 0x0036effe in clone () from /lib/tls/libc.so.6 Thread 3 (Thread 631663536 (LWP 10062)): #0 0x0028e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x0036ba19 in mprotect () from /lib/tls/libc.so.6 #2 0x0814fb3f in Page_AllowAccess (address=0x25fa8000, size=475136) at page.c:149 #3 0x0814f6be in free (address=0xb7ea4ff0) at efence.c:694 #4 0x003232b5 in tzset_internal () from /lib/tls/libc.so.6 #5 0x00323d0e in tzset () from /lib/tls/libc.so.6 #6 0x003288ae in strftime_l () from /lib/tls/libc.so.6 #7 0x0036af6b in vsyslog () from /lib/tls/libc.so.6 #8 0x0036b4df in syslog () from /lib/tls/libc.so.6 #9 0x0806ab08 in slap_send_ldap_result (op=0x25f61e58, rs=0x25a66230) at result.c:585 #10 0x08075952 in fe_op_bind (op=0x25f61e58, rs=0x25a66230) at bind.c:327 #11 0x0807523d in do_bind (op=0x25f61e58, rs=0x25a66230) at bind.c:200 #12 0x0805eac4 in connection_operation (ctx=0x25a662b0, arg_v=0x25f61e58) at connection.c:1133 #13 0x0812d1df in ldap_int_thread_pool_wrapper (xpool=0xb725df58) ---Type <return> to continue, or q <return> to quit--- at tpool.c:478 #14 0x004e5371 in start_thread () from /lib/tls/libpthread.so.0 #15 0x0036effe in clone () from /lib/tls/libc.so.6 Thread 2 (Thread 635861936 (LWP 10061)): #0 ber_get_next (sb=0x25f2ffe8, len=0x25e6427c, ber=0x25f65fd4) at io.c:551 #1 0x0805eed0 in connection_read (s=33) at connection.c:1528 #2 0x0805baa2 in slapd_daemon_task (ptr=0x0) at daemon.c:2461 #3 0x004e5371 in start_thread () from /lib/tls/libpthread.so.0 #4 0x0036effe in clone () from /lib/tls/libc.so.6 Thread 1 (Thread -1208731424 (LWP 10058)): #0 0x0028e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x004e60fd in pthread_join () from /lib/tls/libpthread.so.0 #2 0x0805c621 in slapd_daemon () at daemon.c:2572 #3 0x0804dc9f in main (argc=13, argv=0xbff6ac14) at main.c:860 ------------------------------------------------------------------------------------ It did return the names to my client, which was good, but just crashed after (during) that. Please let me know if I can do anythin else. Thanks!

1 0

Re: (ITS#4883) test000 fails
by ando＠sys-net.it 21 Mar '07

21 Mar '07

Ralf Haferkamp wrote: > unintended or incomplete. Both. Fixed, thanks. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

(ITS#4883) test000 fails
by rhafer＠suse.de 21 Mar '07

21 Mar '07

It seems that the last change in back-monitor.h was either unintended or incomplete. Reverting that change make the test suite working again. Ando, as that was your change, could you please take a deeper look? -- thanks, Ralf

1 0

(ITS#4885) incorrect response macro in ldap_result(3)
by ando＠sys-net.it 21 Mar '07

21 Mar '07

Full_Name: Pierangelo Masarati Version: HEAD OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (87.28.220.33) Submitted by: ando In ldap_result(3) there is mention of LDAP_RES_EXTENDED_PARTIAL, which apparently was replaced by LDAP_RES_INTERMEDIATE since 2.2 or so. p.

1 0

Re: (ITS#4884) Back-config inheritance issue
by ando＠sys-net.it 20 Mar '07

20 Mar '07

I've committed to HEAD a fix that exploits inheritance. The rationale is: - lookup the structural objectClass; starting from it, check it and subordinates for a function that successfully adds the entry - using all objectClass values, collect all, including ancestors, that may be of use in checking configuration. Passes all tests (049->051), and allows to add an overlay using only the overlay's objectClass, provided it's derived from olcOverlayConfig. Please test. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

Re: (ITS#4853) A debug message is printed, from the released version
by ando＠sys-net.it 20 Mar '07

20 Mar '07

Fixed, thanks. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

Re: (ITS#4853) A debug message is printed, from the released version
by Frank.Swasey＠uvm.edu 20 Mar '07

20 Mar '07

This is a cryptographically signed message in MIME format. --------------ms010006030808080804010404 Content-Type: multipart/mixed; boundary="------------080104090705040602090506" This is a multi-part message in MIME format. --------------080104090705040602090506 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit The patch applied in version 1.7.2.12 of refint.c is not complete. It does remove the notice of refint_attribute values, but it leaves the refint_nothing and refint_base using LDAP_DEBUG_ANY instead of also limiting those prints to when LDAP_DEBUG_CONFIG is specified. Attached is a patch deck to correct all three Debug() calls. -- Frank Swasey | http://www.uvm.edu/~fcs Sr Systems Administrator | Always remember: You are UNIQUE, University of Vermont | just like everyone else. "I am not young enough to know everything." - Oscar Wilde (1854-1900) --------------080104090705040602090506 Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0"; name="ITS4853_full.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ITS4853_full.patch" --- refint.c.UVM_refint-head 2007-01-02 16:44:08.000000000 -0500 +++ refint.c 2007-03-20 09:43:17.000000000 -0400 @@ -144,14 +144,14 @@ ip->attr = ad; ip->next = id->attrs; id->attrs = ip; - Debug(LDAP_DEBUG_ANY, "%s: line %d: new attribute <%s>\n", + Debug(LDAP_DEBUG_CONFIG, "%s: line %d: new attribute <%s>\n", fname, lineno, argv[i]); } } else if(!strcasecmp(*argv, "refint_base")) { /* XXX only one basedn (yet) - need validate argument! */ if(id->dn.bv_val) ch_free(id->dn.bv_val); ber_str2bv( argv[1], 0, 0, &dn ); - Debug(LDAP_DEBUG_ANY, "%s: line %d: new baseDN <%s>\n", + Debug(LDAP_DEBUG_CONFIG, "%s: line %d: new baseDN <%s>\n", fname, lineno, argv[1]); if(dnNormalize(0, NULL, NULL, &dn, &id->dn, NULL)) { Debug(LDAP_DEBUG_ANY, "%s: line %d: bad baseDN!\n", fname, lineno, 0); @@ -165,7 +165,7 @@ Debug(LDAP_DEBUG_ANY, "%s: line %d: bad nothingDN!\n", fname, lineno, 0); return(1); } - Debug(LDAP_DEBUG_ANY, "%s: line %d: new nothingDN<%s>\n", + Debug(LDAP_DEBUG_CONFIG, "%s: line %d: new nothingDN<%s>\n", fname, lineno, argv[1]); } else { return(SLAP_CONF_UNKNOWN); --------------080104090705040602090506-- --------------ms010006030808080804010404 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJDzCC AuIwggJLoAMCAQICEAq9rKiduK3HCbKzsBiBodUwDQYJKoZIhvcNAQEEBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDcxNzE2NTcyNloX DTA3MDcxNzE2NTcyNlowRjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEjMCEG CSqGSIb3DQEJARYURnJhbmsuU3dhc2V5QHV2bS5lZHUwggEiMA0GCSqGSIb3DQEBAQUAA4IB DwAwggEKAoIBAQCzhSmesaR8qf2y5cNt0qa27m42Kq3Bwubs28CzSxR1uRUaRZUfL/C2FEFV kKSat6da5b19UEWxM1giaWvLeDtQE5Tok8GhN8LNgScTiSEM6gFWnL0o7A9W7oAj42dfFvBV md7/u7nSJoAP3Wt9cU3TBJBh99U89EzIYLNik8iVhzbwfNmisxmuR5870AHURoR1sN/X4jWx q5114Rv8r60+bVitlXL7P20Z2S9+va9+a7+C1P/yJLPq1GK8+X9uaoUaGHlapBeBYNu3QWQG Q+mF+QuidS01jbaburvJxUm7dVO3QRt1PovVhlidv89eqcH8n4h7xSG1IG3teNJkschdAgMB AAGjMTAvMB8GA1UdEQQYMBaBFEZyYW5rLlN3YXNleUB1dm0uZWR1MAwGA1UdEwEB/wQCMAAw DQYJKoZIhvcNAQEEBQADgYEAblV8ye5ZLs/y3DX0W3NU67N2T6tOSZ1609L+BRWB/Md7RDFd Cm8AXFIldDLzkyPFqs9WpgAQLvZ0gRXQ8aqwYEBB3WlZzkpUS+YTuY6X9wjcroMjHCyWNpq0 /joDumCNSEWiZJ6AZMRom9Z/P6foBxXmgCBKVq/O0mGqgArlxdkwggLiMIICS6ADAgECAhAK vayonbitxwmys7AYgaHVMA0GCSqGSIb3DQEBBAUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNjA3MTcxNjU3MjZaFw0wNzA3MTcxNjU3MjZa MEYxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIzAhBgkqhkiG9w0BCQEWFEZy YW5rLlN3YXNleUB1dm0uZWR1MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAs4Up nrGkfKn9suXDbdKmtu5uNiqtwcLm7NvAs0sUdbkVGkWVHy/wthRBVZCkmrenWuW9fVBFsTNY Imlry3g7UBOU6JPBoTfCzYEnE4khDOoBVpy9KOwPVu6AI+NnXxbwVZne/7u50iaAD91rfXFN 0wSQYffVPPRMyGCzYpPIlYc28HzZorMZrkefO9AB1EaEdbDf1+I1sauddeEb/K+tPm1YrZVy +z9tGdkvfr2vfmu/gtT/8iSz6tRivPl/bmqFGhh5WqQXgWDbt0FkBkPphfkLonUtNY22m7q7 ycVJu3VTt0EbdT6L1YZYnb/PXqnB/J+Ie8UhtSBt7XjSZLHIXQIDAQABozEwLzAfBgNVHREE GDAWgRRGcmFuay5Td2FzZXlAdXZtLmVkdTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA A4GBAG5VfMnuWS7P8tw19FtzVOuzdk+rTkmdetPS/gUVgfzHe0QxXQpvAFxSJXQy85MjxarP VqYAEC72dIEV0PGqsGBAQd1pWc5KVEvmE7mOl/cI3K6DIxwsljaatP46A7pgjUhFomSegGTE aJvWfz+n6AcV5oAgSlavztJhqoAK5cXZMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUF ADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2Fw ZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNh dGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVt YWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4X DTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxV c1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J 8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9I BH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0f BDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1h aWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRl TGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aU nX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3d qZw5jowgT2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCA2Qw ggNgAgEBMHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQ dHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENB AhAKvayonbitxwmys7AYgaHVMAkGBSsOAwIaBQCgggHDMBgGCSqGSIb3DQEJAzELBgkqhkiG 9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA3MDMyMDEzNTE0NlowIwYJKoZIhvcNAQkEMRYEFH3P vHIi8xXKD1kPu1urTjvGs7UyMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZI hvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGFBgkr BgEEAYI3EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGlu ZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWlu ZyBDQQIQCr2sqJ24rccJsrOwGIGh1TCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYT AlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNU aGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQCr2sqJ24rccJsrOwGIGh1TAN BgkqhkiG9w0BAQEFAASCAQCKsfzObajHIgMefZW2QJwF0uhq3rkjCMyMCcWmuRi8jMBu1E8K 5HaZVQHExEyiDeqD+eGW1lDps4u1nP4/pIjVh94RlXUzpG0gE5zW0d56Oz+FUrjavTN2UkcX CBpYUYDjlQ9TneqvUXRWwLcJBo9JGnCElVy7o4gm/hJObB28xaxIrNv6cYmWV0khianRwtS2 cfystVgiI19NlBHPJIO8MZv6J/Do75tfaJpQBqIiSaT+XABWrtww6sjpTw9ooUzczWQEjoOF dXVjSZE+1EeWmPflbE/6qE2KCRiX8pxgswWztgLnm7lvO3qxONysME/Wc9zGqlWTHZHYHium qrEvAAAAAAAA --------------ms010006030808080804010404--

1 0

(ITS#4884) Back-config inheritance issue
by ando＠sys-net.it 20 Mar '07

20 Mar '07

Full_Name: Pierangelo Masarati Version: HEAD (re23,...) OS: irrelevant URL: Submission from: (NULL) (87.28.220.33) Submitted by: ando I think I've spotted a potential issue in back-config. When creating a custom object, say an overlay, the configuration objectClass should inherit from olcOverlayConfig. While adding the object via LDAP, however, if the ancestor class is not explicitly listed, the derived object must provide a co_ldadd() hook, otherwise addition fails. It would be more sound, IMHO, to have something like: - if the structural objectClass provides a co_ldadd() hook, use it; it is that hook's responsibility to call the superior's one if required; - if it doesn't, then climb the inheritance tree and call co_ldadd() for the first occurrence of a valid one. In case of multiple inheritance, issues may arise. In those cases, we could: - require an explicit co_ldadd() in the derived object to resolve the ambiguity (this is basically what C++ does) - otherwise, co_ldadd() should perhaps be called for the first occurrence in all branches of multiple inheritance, and it should be able to either create the entry, or modify an existing entry. handlers should be called in order of inheritance. Currently, the code uses all defined objectClasses and stops the first time a hook is available and it does not fail. p.

1 0

(ITS#4883) test000 fails
by dieter＠dkluenter.de 20 Mar '07

20 Mar '07

Full_Name: Dieter Kluenter Version: HEAD OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (80.187.212.14) I checked out todays cvs and failed with test000, slapd.1.log shows @(#) $OpenLDAP: slapd 2.X (Mar 20 2007 11:57:18) $ dieter@magenta:/work/ldap-src/servers/slapd ldap_pvt_gethostbyname_a: host=magenta, r=0 daemon_init: ldap://localhost:9011/ daemon_init: listen on ldap://localhost:9011/ daemon_init: 1 listeners to open... ldap_url_parse_ext(ldap://localhost:9011/) daemon: listener initialized ldap://localhost:9011/ daemon_init: 2 listeners opened ldap_create lt-slapd init: initiated server. slap_sasl_init: initialized! bdb_back_initialize: initialize BDB backend bdb_back_initialize: Sleepycat Software: Berkeley DB 4.4.20: (January 10, 2006) hdb_back_initialize: initialize HDB backend hdb_back_initialize: Sleepycat Software: Berkeley DB 4.4.20: (January 10, 2006) => str2entry: "dn: vendorName: The OpenLDAP Project <http://www.openldap.org/> " >>> dnPrettyNormal: <> <<< dnPrettyNormal: <>, <> <= str2entry() -> 0x822002c bdb_db_init: Initializing BDB database >>> dnPrettyNormal: <o=OpenLDAP Project,l=Internet> => ldap_bv2dn(o=OpenLDAP Project,l=Internet,0) <= ldap_bv2dn(o=OpenLDAP Project,l=Internet)=0 => ldap_dn2bv(272) <= ldap_dn2bv(o=OpenLDAP Project,l=Internet)=0 => ldap_dn2bv(272) <= ldap_dn2bv(o=openldap project,l=internet)=0 <<< dnPrettyNormal: <o=OpenLDAP Project,l=Internet>, <o=openldap project,l=internet> >>> dnPrettyNormal: <cn=Monitor> => ldap_bv2dn(cn=Monitor,0) <= ldap_bv2dn(cn=Monitor)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=Monitor)=0 > ldap_dn2bv(272) <= ldap_dn2bv(cn=monitor)=0 <<< dnPrettyNormal: <cn=Monitor>, <cn=monitor> >>> dnNormalize: <cn=Subschema> => ldap_bv2dn(cn=Subschema,0) <= ldap_bv2dn(cn=Subschema)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=subschema)=0 <<< dnNormalize: <cn=subschema> matching_rule_use_init [...] t-slapd startup: initiated. backend_startup_one: starting "cn=config" config_back_db_open config_build_entry: "cn=config" config_build_entry: "cn=schema" config_build_entry: "cn={0}core" config_build_entry: "cn={1}cosine" config_build_entry: "cn={2}corba" config_build_entry: "cn={3}java" config_build_entry: "cn={4}inetorgperson" config_build_entry: "cn={5}misc" config_build_entry: "cn={6}nis" config_build_entry: "cn={7}openldap" config_build_entry: "cn={8}duaconf" config_build_entry: "cn={9}dyngroup" config_build_entry: "cn={10}ppolicy" config_build_entry: "olcDatabase={-1}frontend" config_build_entry: "olcDatabase={0}config" config_build_entry: "olcDatabase={1}bdb" config_build_entry: "olcDatabase={2}monitor" backend_startup_one: starting "o=OpenLDAP Project,l=Internet" bdb_db_open: o=OpenLDAP Project,l=Internet bdb_db_open: Warning - No DB_CONFIG file found in directory /work/ldap-src/tests/testrun/db.1.a: (2) Expect poor performance for suffix o=OpenLDAP Project,l=Internet. bdb_db_open: dbenv_open(/work/ldap-src/tests/testrun/db.1.a) ====> bdb_cache_release_all backend_startup_one: bi_db_open failed! (1) lt-slapd shutdown: initiated ====> bdb_cache_release_all bdb_db_close: alock_close failed lt-slapd destroy: freeing system resources. slapd stopped. connections_destroy: nothing to destroy. my configure parameters export CFLAGS="-DLDAP_DEVEL" ./configure \ --prefix=/opt/openldap \ --enable-dynamic \ --enable-aci \ --enable-modules \ --enable-rewrite \ --enable-bdb=yes \ --enable-hdb=yes \ --enable-java=mod \ --enable-ldap=mod \ --enable-monitor=yes \ --enable-meta=mod \ --enable-perl=mod \ --enable-relay=mod \ --enable-sql=mod \ --enable-overlays=mod -Dieter

1 0

Re: (ITS#4882) Add doesnt work <OpenStruct message="unknown result (64)", code=64>
by ando＠sys-net.it 20 Mar '07

20 Mar '07

sxm20(a)yahoo.com wrote: > Full_Name: Shailesh Mangal > Version: 2.2.29 > OS: Windows > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (69.228.83.104) > > > While trying to add entry from Ruby's netLdap library. > > [result = @ldap_con.add(:dn => dn, :attributes => attr)] > > I get following error message. > <OpenStruct message="unknown result (64)", code=64> > > I have also tried it on Linux (debian), getting the same error message The ITS is not for help on software usage; please direct software usage questions to openldap-software. In any case, 2.2.29 is ancient, so even in the case of a bug there are no chances it gets fixed unless it is still present in currently released code. In your case, the error is likely to be on the user's side; see the FAQ for directions about typical user errors; see RFC4511 (or ldap.h) for mapping between result codes and diagnostics. This ITS will be closed. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

(ITS#4882) Add doesnt work <OpenStruct message="unknown result (64)", code=64>
by sxm20＠yahoo.com 19 Mar '07

19 Mar '07

Full_Name: Shailesh Mangal Version: 2.2.29 OS: Windows URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (69.228.83.104) While trying to add entry from Ruby's netLdap library. [result = @ldap_con.add(:dn => dn, :attributes => attr)] I get following error message. <OpenStruct message="unknown result (64)", code=64> I have also tried it on Linux (debian), getting the same error message

1 0

(ITS#4881) ldapsearch, SSL and segmentation fault
by andrej.groups＠gmail.com 19 Mar '07

19 Mar '07

Full_Name: Andrej Ricnik Version: ldapsearch 2.3.21 OS: Slackware 11 URL: Submission from: (NULL) (138.235.105.2) I'm trying to use ldapsearch against Novell eDir 8.7.3.9 (on Solaris) which works fine when used w/o encryption. If I use the self-signed Cert created on the eDir server ldapsearch segfaults. This works fine (returns the expected 46 DNs): ldapsearch -D cn=wpsbind,ou=wcm,ou=systemusers,ou=users,o=myorg -W -h dev4.kdc.myorg.org -x -s sub -LLL '(cn=*)' This one segfaults after the 45th DN: ldapsearch -ZZ -D cn=wpsbind,ou=wcm,ou=systemusers,ou=users,o=myorg -W -h dev4.kdc.myorg.org -x -s sub -LLL '(cn=*)' It looks similar to ITN# 889 ...

1 0

Re: (ITS#4868) Binary Attribute Patch(es)
by ando＠sys-net.it 19 Mar '07

19 Mar '07

vargok(a)yahoo.com wrote: > Additionally, just FYI, it appears that the regular/standard OpenLDAP > (at least as of 2.3.32) BDB-based backend returns > "userCertificate;binary" just fine (and, actually, all the time, even > when requesting "userCertificate"). I would've expected them to > behave the same way. Right. Time permitting, I'll check why back-sql behaves differently and, in case, how to fix it. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

Re: (ITS#4868) Binary Attribute Patch(es)
by vargok＠yahoo.com 19 Mar '07

19 Mar '07

Additionally, just FYI, it appears that the regular/standard OpenLDAP (at least as of 2.3.32) BDB-based backend returns "userCertificate;binary" just fine (and, actually, all the time, even when requesting "userCertificate"). I would've expected them to behave the same way. ----- Original Message ---- From: Pierangelo Masarati <ando(a)sys-net.it> To: Kevin Vargo <vargok(a)yahoo.com> Cc: openldap-its(a)openldap.org Sent: Wednesday, March 14, 2007 5:05:52 PM Subject: Re: (ITS#4868) Binary Attribute Patch(es) Kevin Vargo wrote: > However, there remains a problem: other LDAP Servers appear to return > the 'attribute-name' requested (userCertificate;binary::) to describe > the data. Now that the data is being returned, it's being returned > without the ";binary" option -- as 'userCertificate::'. Per > ITS#3113, ";binary" is obsoleted? To be honest, I'm not sure I have ever clearly understood that ";binary" issue, and I don't have time to dig out the documentation, learn about it, and check the code, since the whole stuff seems to be obsolete. > Is there a compatibility mode that can be optioned to support this? None that I know of. > Obsoleted and back-wards compatibility being in conflict..... I think compatibility with obsolete stuff is something that may easily get in conflict with open source, volunteer developed software. Volunteers tend to concentrate scarce resources on important things, and preserving compatibility with obsolete (often broken) stuff is first of all a waste of scarce resources, and second, but not least, reduces pressure on obsolete (broken) software makers, which typically are not volunteers but actually get paid for (obsolete/broken stuff). Having said this, you may find volunteers that, pushed by their own needs like to spend time supporting obsolete/broken stuff for the simple reason they need it. > i.e. > is there a way to say "return the attribute by name-requested instead > of schema-name?" No. This question has been raised many times, and the answer has always been like that. All you could do is hack slap_send_search_entry() in servers/slapd/result.c. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------ ____________________________________________________________________________________ Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html

1 0

(ITS#4880) HAVE_POSIX_TERMIOS -> HAVE_TERMIOS_H
by ed＠fxq.nl 18 Mar '07

18 Mar '07

Full_Name: Ed Schouten Version: 2.3.x and 2.4.x OS: FreeBSD URL: Submission from: (NULL) (83.180.2.78) The FreeBSD folks are planning on removing the old <sgtty.h> interface from their operating system. On FreeBSD, OpenLDAP still uses this header file, though there is some nice termios code in the source. It isn't used on FreeBSD at the moment, because the code doesn't use the same naming as the definition made by autoconf. A simple %s/HAVE_POSIX_TERMIOS/HAVE_TERMIOS_H/ on the sourcetree fixes this.

1 0

(ITS#4879) URL parse/unparse troubles
by h.b.furuseth＠usit.uio.no 17 Mar '07

17 Mar '07

Full_Name: Hallvard B Furuseth Version: HEAD OS: Linux URL: Submission from: (NULL) (129.240.202.105) Submitted by: hallvard Here are some URLs parsing/building bugs in libldap/url.c. Some may be design bugs. Possibly some fixes will need backwards bug-compatibility. I show URLs converted from string to LDAPURLDesc format with ldap_url_parse(), back to string format with ldap_url_desc2str() when the result differs from the original, back to LDAPURLDesc... ================ The url.c Novell kludge does not work (for the example URL). If the bug is old and nobody has complained, maybe it should be removed. If it's fixed instead, note that the code looks like it'll handle Novell URLs with '/' in components after hostport: ldap_url_parse_ext() does strchr( url, '/' ) very early to find the end of the hostport. ldap://111.222.333.444:389??cn=abc,o=company -> error 5 (LDAP_URL_ERR_BADURL) Example URL without port number: ldap://111.222.333.444??cn=abc,o=company -> host "111.222.333.444??cn=abc,o=company", DN NULL -> ldap://111.222.333.444??cn=abc,o=company:389/??base ================ ldap_url_desc2str() outputs IPv6 host addresses as "addr" rather than "[addr]". (LDAPURLDesc does not contain the '[]'s in .lud_host, nor any flag which says it's an IPv6 host address). I don't know the syntax of such addresses, but I seem to remember they contains ':'s. If so the parser could fail if an IPv6 address does not contains ':', and the URL builder could test for ':' to determine if there should be [] around the host part. Also, what does stuff between the ']' and ':port' mean? Should anything be allowed there? ldap://[::1]what's this:222/ -> host "::1", port 222 -> ldap://::1:222/??base -> error 5 (LDAP_URL_ERR_BADURL) ================ Converting "%00" to char* should return an error, since the char* will not match the source URL: ldapi://a%00b/cn=d%00e -> host "a", DN "cn=d" -> ldapi://a/cn=d??base ================ The RFCs 4516/2255 hostport part has grammar [host [":" port]], but ldap_url_desc2str() produces [host][":" port]. ldap:// -> host NULL, port 389 -> ldap://:389/??base That's OK as an ldap_url_parse() OpenLDAP extension, but not as ldap_url_desc2str() output given to non-OpenLDAP applications. ================ While I'm writing, I wonder if OpenLDAP 2.4 could omit defaults and final "?"s from the ldap_url_desc2str() output. E.g. ldap:// would become ldap:// and not ldap://:389/??base. But maybe we get into trouble if ldap.conf has another port or something. ================ ldapi URL (un)parsing has several problems: ldap_url_parse() always treats ':' as a host:port separator. Thus one can produce an ldapi LDAPURLDesc with a meaningless port. However ldap_url_desc2str() does not URL-escape ':', and it also takes port!=0 to mean it is not an ldapi URL and needs no '/'-escaping. Similarly filenames with initial '[' do not work. ldapi://%2Ftmp%2Ffoo%3A222/ -> host "/tmp/foo:222" (correct) -> ldapi://%2Ftmp%2Ffoo:222/??base -> host "/tmp/foo", port 222 -> ldapi:///tmp/foo:222/??base -> host NULL, DN "tmp/foo:222/" ldapi://%2Ftmp%2Ffoo:000/ -> host "/tmp/foo" -> ldapi://%2Ftmp%2Ffoo/??base ldapi://%2Ftmp%2Ffoo:bar/ -> error 5 (LDAP_URL_ERR_BADURL) ==== The current implementation would handle some non-Unix ldapi filenames wrong. (They'll need well-defined URL-escaping rules if they get implemented, so it might as well be fixed now.) Of course these can also be strange Unix relative filenames... Windows-like filenames: ldapi://C%3A%2Fldapi/ -> host "C:/ldapi" -> ldapi://C:%2Fldapi/??base -> error 5 (LDAP_URL_ERR_BADURL) Tops-20-like filenames resemble IPv6 addresses (not that I expect to port OpenLDAP to Tops-20:-) ldapi://[ldap.var.run]ldapi/ -> host "ldap.var.run" -> ldapi://ldap.var.run/??base URL-escaping the '[' and ']' does not help; the '[' is lost: ldapi://%5Bldap.var.run%5Dldapi/ -> host "ldap.var.run]ldapi" -> ldapi://ldap.var.run%5Dldapi/??base

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs