openldap-bugs

openldap-bugs@openldap.org

20960 discussions

Re: (ITS#5898) test044 abort with back-ldif
by ando＠sys-net.it 30 Jan '09

30 Jan '09

h.b.furuseth(a)usit.uio.no wrote: > Pierangelo Masarati writes: >> Probably related; in any case, misused in slapo-dynlist(5). Now slapd >> doesn't assert() any more. However, the test fails because back-ldif >> does not implement compare, and falls back to be_fetch(), which does not >> trigger dynlist expansion. > > Yes, the "compare without help from the backend" functionality has been > broken for years - which I presume means it's hard to fix, or needs a > different design. > > Should we patch it over by adding Compare to back-ldif and whatever else > lacks it? Or is this a "fix coming Real Soon Now" issue so it's good > to have this reminder from a backend which doesn't provide Compare? Not sure whether it's about to come sooner or later, but the issue is always about be_fetch, aka bi_entry_get_rw() whose design Is Broken (TM) (actually, it broke when overlays came into play). I don't know how useful it would be to have back-ldif directly implement compare, as soon as one only uses it for back-config and not for a real storage with stacked overlays (however I note that back-config needs at least to nicely interoperate with one overlay: slapo-syncprov). 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 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

1 0

Re: (ITS#5898) test044 abort with back-ldif
by h.b.furuseth＠usit.uio.no 30 Jan '09

30 Jan '09

Pierangelo Masarati writes: > Probably related; in any case, misused in slapo-dynlist(5). Now slapd > doesn't assert() any more. However, the test fails because back-ldif > does not implement compare, and falls back to be_fetch(), which does not > trigger dynlist expansion. Yes, the "compare without help from the backend" functionality has been broken for years - which I presume means it's hard to fix, or needs a different design. Should we patch it over by adding Compare to back-ldif and whatever else lacks it? Or is this a "fix coming Real Soon Now" issue so it's good to have this reminder from a backend which doesn't provide Compare? -- Hallvard

1 0

Re: (ITS#5915) Some man pages still only talk about slapd.conf
by h.b.furuseth＠usit.uio.no 30 Jan '09

30 Jan '09

hyc(a)symas.com writes: > I guess for this release (and probably for 2.5) we're just going to > have to document both, as cumbersome as that will be. When we get to > to 2.6/3.0 and drop support for slapd.conf we'll have to come back > thru again and delete the slapd.conf references from all the > docs. Unless anyone has a better idea... I'm not sure I see the problem, except that Someone(TM) must do the work... For each configuration keyword, use two headers in the manpages: Both the slapd.conf syntax and the cn=config syntax. Explain at the beginning of slapd.conf.5 or slapd-config.5. We'll be deleting most of the other one, since they are mostly duplicates. Other manpages need just one-line reminder for explanation. There'll be exceptions that spell things out too differently, or use slightly different parameters in slapd.conf and cn=config. Keep them in just slapd.conf-syntax, and add a separate cn=config attribute description below. Likely that'll only need to explain the difference. Don't go trough literary contortions to fit them both into the same description. Some of these will likely be things that could use some cleanup in the code anyway, bringing the two config formats in sync. Take a random sample of the slapd.conf-syntax example sections and replace with their cn=config equivalent. Ensure all example sections say either "slapd.conf example" or "cn=config example". slapd.conf.5 and slapd-config.5 themselves will need sections about how they work as interfaces to configuration, separate from the configuration keywords/attributes themselves. Since we are moving towards cn=config, I suppose it's that one which should keep the actual keyword/attribute descriptions. Or they could move to a third file. -- Hallvard

1 0

Re: (ITS#5898) test044 abort with back-ldif
by ando＠sys-net.it 30 Jan '09

30 Jan '09

h.b.furuseth(a)usit.uio.no wrote: >> When using the back-ldif backend with test044, it aborts: > > Probably ITS#5340. Probably related; in any case, misused in slapo-dynlist(5). Now slapd doesn't assert() any more. However, the test fails because back-ldif does not implement compare, and falls back to be_fetch(), which does not trigger dynlist expansion. 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 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

1 0

Re: (ITS#5913) supportedSASLMechanisms EXTERNAL not Work
by ando＠sys-net.it 30 Jan '09

30 Jan '09

jarbas.peixoto(a)gmail.com wrote: > Full_Name: Jarbas Peixoto Junior > Version: 2.4.11 > OS: Debian Lenny > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (200.152.43.195) > > > I have two servers: > > * Server A: Debian Etch - Works Fine > > * Server B: Debian Lenny - Do not Works supportedSASLMechanisms EXTERNAL > > In Server A I have: > > # ldapsearch -v -H ldap://server-Etch -b "" -LLL -s base supportedSASLMechanisms > -ZZ > ldap_initialize( ldap://server-Etch ) > SASL/EXTERNAL authentication started > SASL username: emailAddress=jarbas.peixoto(a)previdencia.gov.br,CN=jarbas.peixoto,OU=DATAPREV,O=Previdencia > Social,L=Campo Grande,ST=Mato Grosso do Sul,C=BR > SASL SSF: 0 > filter: (objectclass=*) > requesting: supportedSASLMechanisms > dn: > supportedSASLMechanisms: PLAIN > supportedSASLMechanisms: DIGEST-MD5 > supportedSASLMechanisms: LOGIN > supportedSASLMechanisms: NTLM > supportedSASLMechanisms: CRAM-MD5 > supportedSASLMechanisms: EXTERNAL > > In Server B I have: > > # ldapsearch -v -H ldap://server-Lenny -b "" -LLL -s base > supportedSASLMechanisms -ZZ > ldap_initialize( ldap://server-Lenny:389/??base ) > ldap_start_tls: Connect error (-11 ^^^ start TLS is failing. There is no evidence of a bug in the software; likely either the client or the server's TLS is misconfigured. Please direct software usage questions to the openldap-software list. 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 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

1 0

Re: (ITS#5915) Some man pages still only talk about slapd.conf
by hyc＠symas.com 30 Jan '09

30 Jan '09

ghenry(a)OpenLDAP.org wrote: > Full_Name: Gavin Henry > Version: > OS: > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (92.41.236.102) > Submitted by: ghenry > > > Some discussion will be needed on the best way to talk about config. We don't > want to list everything twice for both formats...lots of slapd.conf written > throughout most (5/8) man pages. I guess for this release (and probably for 2.5) we're just going to have to document both, as cumbersome as that will be. When we get to to 2.6/3.0 and drop support for slapd.conf we'll have to come back thru again and delete the slapd.conf references from all the docs. Unless anyone has a better idea... -- -- 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

(ITS#5915) Some man pages still only talk about slapd.conf
by ghenry＠OpenLDAP.org 30 Jan '09

30 Jan '09

Full_Name: Gavin Henry Version: OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (92.41.236.102) Submitted by: ghenry Some discussion will be needed on the best way to talk about config. We don't want to list everything twice for both formats...lots of slapd.conf written throughout most (5/8) man pages. Thanks.

1 0

(ITS#5914) Update all man pages that only "SEE ALSO slapd.conf(5)" to list slapd-config(5)
by ghenry＠OpenLDAP.org 30 Jan '09

30 Jan '09

Full_Name: Gavin Henry Version: HEAD OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (92.41.164.91) Submitted by: ghenry Will commit shortly.

1 0

(ITS#5913) supportedSASLMechanisms EXTERNAL not Work
by jarbas.peixoto＠gmail.com 29 Jan '09

29 Jan '09

Full_Name: Jarbas Peixoto Junior Version: 2.4.11 OS: Debian Lenny URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (200.152.43.195) I have two servers: * Server A: Debian Etch - Works Fine * Server B: Debian Lenny - Do not Works supportedSASLMechanisms EXTERNAL In Server A I have: # ldapsearch -v -H ldap://server-Etch -b "" -LLL -s base supportedSASLMechanisms -ZZ ldap_initialize( ldap://server-Etch ) SASL/EXTERNAL authentication started SASL username: emailAddress=jarbas.peixoto(a)previdencia.gov.br,CN=jarbas.peixoto,OU=DATAPREV,O=Previdencia Social,L=Campo Grande,ST=Mato Grosso do Sul,C=BR SASL SSF: 0 filter: (objectclass=*) requesting: supportedSASLMechanisms dn: supportedSASLMechanisms: PLAIN supportedSASLMechanisms: DIGEST-MD5 supportedSASLMechanisms: LOGIN supportedSASLMechanisms: NTLM supportedSASLMechanisms: CRAM-MD5 supportedSASLMechanisms: EXTERNAL In Server B I have: # ldapsearch -v -H ldap://server-Lenny -b "" -LLL -s base supportedSASLMechanisms -ZZ ldap_initialize( ldap://server-Lenny:389/??base ) ldap_start_tls: Connect error (-11 # ldapsearch -v -H ldap://server-Lenny -b "" -LLL -s base supportedSASLMechanisms -ZZ -d 1 ldap_url_parse_ext(ldap://server-Lenny) ldap_create ldap_url_parse_ext(ldap://server-Lenny:389/??base) ldap_extended_operation_s ldap_extended_operation ldap_send_initial_request ldap_new_connection 1 1 0 ldap_int_open_connection ldap_connect_to_host: TCP server-Lenny:389 ldap_new_socket: 3 ldap_prepare_socket: 3 ldap_connect_to_host: Trying 10.82.0.234:389 ldap_pvt_connect: fd: 3 tm: -1 async: 0 ldap_open_defconn: successful ldap_send_server_request ber_scanf fmt ({it) ber: ber_scanf fmt ({) ber: ber_flush2: 31 bytes to sd 3 ldap_result ld 0x9d73280 msgid 1 wait4msg ld 0x9d73280 msgid 1 (infinite timeout) wait4msg continue ld 0x9d73280 msgid 1 all 1 ** ld 0x9d73280 Connections: * host: www-mmldap port: 389 (default) refcnt: 2 status: Connected last used: Thu Jan 29 18:17:22 2009 ** ld 0x9d73280 Outstanding Requests: * msgid 1, origid 1, status InProgress outstanding referrals 0, parent count 0 ld 0x9d73280 request count 1 (abandoned 0) ** ld 0x9d73280 Response Queue: Empty ld 0x9d73280 response count 0 ldap_chkResponseList ld 0x9d73280 msgid 1 all 1 ldap_chkResponseList returns ld 0x9d73280 NULL ldap_int_select read1msg: ld 0x9d73280 msgid 1 all 1 ber_get_next ber_get_next: tag 0x30 len 12 contents: read1msg: ld 0x9d73280 msgid 1 message type extended-result ber_scanf fmt ({eAA) ber: read1msg: ld 0x9d73280 0 new referrals read1msg: mark request completed, ld 0x9d73280 msgid 1 request done: ld 0x9d73280 msgid 1 res_errno: 0, res_error: <>, res_matched: <> ldap_free_request (origid 1, msgid 1) ldap_free_connection 0 1 ldap_free_connection: refcnt 1 ldap_parse_extended_result ber_scanf fmt ({eAA) ber: ldap_parse_result ber_scanf fmt ({iAA) ber: ber_scanf fmt (}) ber: ldap_msgfree ldap_err2string ldap_start_tls: Connect error (-11) In the /var/log/syslog I have: Jan 29 18:17:22 server-Lenny slapd[12945]: conn=99 fd=21 ACCEPT from IP=10.82.0.234:50441 (IP=0.0.0.0:389) Jan 29 18:17:22 server-Lenny slapd[12945]: conn=99 op=0 EXT oid=1.3.6.1.4.1.1466.20037 Jan 29 18:17:22 server-Lenny slapd[12945]: conn=99 op=0 STARTTLS Jan 29 18:17:22 server-Lenny slapd[12945]: conn=99 op=0 RESULT oid= err=0 text= Jan 29 18:17:22 server-Lenny slapd[12945]: conn=99 fd=21 closed (TLS negotiation failure) This is very important for use openldap with user certificates. Anybody have a help for me? Tanks!

1 0

Re: (ITS#5912) Meta modify increment feature
by ando＠sys-net.it 29 Jan '09

29 Jan '09

Fixed in HEAD; please test. Thanks, 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 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

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