Full_Name: Dave Horsfall
Version: 2.4.7
OS: FreeBSD 4.10-STABLE
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (192.65.182.30)
On setting the general client timeout with LDAP_OPT_TIMEOUT and performing
a search on a simulated hung server ("nc -l 389"), I get a coredump:
assertion "r != NULL" failed: file "error.c", line 272
GDB:
(gdb) bt
#0 0x28136748 in kill () from /usr/lib/libc.so.4
#1 0x2817803e in abort () from /usr/lib/libc.so.4
#2 0x28154033 in __assert () from /usr/lib/libc.so.4
#3 0x280bf519 in ldap_parse_result (ld=0x8050000, r=0x0, errcodep=0xbfbfdb2c,
matcheddnp=0x0, errmsgp=0x0, referralsp=0x0, serverctrls=0x0, freeit=0)
at error.c:272
#4 0x280bf455 in ldap_result2error (ld=0x8050000, r=0x0, freeit=0)
at error.c:222
#5 0x280c016d in ldap_search_s (ld=0x8050000, base=0x0, scope=2,
filter=0xbfbff450 "(uid=daveh)", attrs=0xbfbfdbd8, attrsonly=0,
res=0xbfbfdbe0) at search.c:392
#6 0x8049e9b in main (argc=0, argv=0xbfbff8b8) at lget.c:662
thm(a)duke.edu wrote:
> Full_Name: Hunter Matthews
> Version: ldapsearch 2.3.27
> OS: Centos-5
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (152.3.12.219)
>
>
> ldapsearch -h
> shows all (I assume) the options I can use.
>
> But the man page is missing -E at least.
The -E option was added in a later release. The current 2.3 release is 2.3.39;
you're far out of date. This ITS will be closed.
--
-- 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/
Full_Name: Hunter Matthews
Version: ldapsearch 2.3.27
OS: Centos-5
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (152.3.12.219)
ldapsearch -h
shows all (I assume) the options I can use.
But the man page is missing -E at least.
Full_Name: Dieter Kluenter
Version: HEAD
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (84.142.223.222)
test 028 fails with segmentation fault
gdb output
Reading symbols from
/work/ldap-src/servers/slapd/back-ldap/.libs/back_ldap-2-devel.so.0...done.
Loaded symbols for ../servers/slapd/back-ldap/.libs/back_ldap-2-devel.so.0
Reading symbols from
/work/ldap-src/servers/slapd/overlays/.libs/rwm-2-devel.so.0...done.
Loaded symbols for ../servers/slapd/overlays/.libs/rwm-2-devel.so.0
Core was generated by `/work/ldap-src/servers/slapd/.libs/lt-slapd -Ta -d 0 -f
/work/ldap-src/tests/te'.
Program terminated with signal 11, Segmentation fault.
#0 0xb78926d4 in rwm_cf_gen (c=0xbff812dc) at rwm.c:1771
1771 (struct ldaprwmap *)on->on_bi.bi_private;
(gdb) bt
#0 0xb78926d4 in rwm_cf_gen (c=0xbff812dc) at rwm.c:1771
#1 0x0806eb67 in config_set_vals (Conf=0xb789a228, c=0xbff812dc) at
config.c:314
#2 0x0806f049 in config_add_vals (Conf=0xb789a228, c=0xbff812dc) at
config.c:383
#3 0x080f05be in over_db_config (be=0x8275840, fname=0x822e008
"/work/ldap-src/tests/testrun/slapadd.conf", lineno=98,
argc=2, argv=0x8255648) at backover.c:151
#4 0x0807035f in read_config_file (fname=0x822e008
"/work/ldap-src/tests/testrun/slapadd.conf", depth=0, cf=0x0,
cft=0x81c88a0) at config.c:792
#5 0x080667c4 in read_config (fname=0x822e008
"/work/ldap-src/tests/testrun/slapadd.conf", dir=0x0) at bconfig.c:3455
#6 0x080f5d18 in slap_tool_init (progname=0x818a920 "slapadd", tool=1, argc=10,
argv=0xbff8ac74) at slapcommon.c:523
#7 0x080f3acc in slapadd (argc=10, argv=0xbff8ac74) at slapadd.c:73
#8 0x0805d013 in main (argc=10, argv=0xbff8ac74) at main.c:645
(gdb)
(gdb) down 0xb78926d4
#8 0x0805d013 in main (argc=10, argv=0xbff8ac74) at main.c:645
645 rc = tools[i].func( argc, argv
);
(gdb) down 0x0806eb67
#0 0xb78926d4 in rwm_cf_gen (c=0xbff812dc) at rwm.c:1771
1771 (struct ldaprwmap *)on->on_bi.bi_private;
(gdb)
-Dieter
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245341>
has a patch for compiling against gcrypt, don't know it it needs work.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
Full_Name: Quanah Gibson-Mount
Version: 2.4.7
OS: Linux 2.6
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (66.92.25.194)
If one enables lanman hashes while building OpenLDAP, and using GnuTLS instead
of OpenSSL, the build will fail as the lanman code has OpenSSL specific
assumptions.
--Quanah
Full_Name: Raphael Ouazana
Version: HEAD, RE24, RE23
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (164.2.255.244)
Hi,
I repost this here as I think the discussion was lost in a closed ITS (#4860).
The two solutions (other operation or previous behavior) would be fine for us,
but I have not really time to make a patch for the moment.
Le Sam 10 novembre 2007 16:37, ando(a)sys-net.it a .crit :
>> Below I represent sets in {element1, element2} notation, to describe
the
>> current behaviour (in HEAD) for slap_set_join on the '+' operation:
>> - {"One", "Two"} + {"Three", "Four"} ==> {"OneThree", "OneFour",
>> "TwoThree", "TwoFour"}
>> - {"One", "Two"} + {""} ==> {"One", "Two"}
>> - {"One", "Two"} + {NULL} ==> {"One", "Two"}
>
> Although sets lack a specification, I think this behavior is desirable
> in many cases: adding NULL is equivalent to adding EMPTY ("").
The problem is that {NULL} is equivalent to NULL, ie the empty set.
>> Consider the following set:
>> set="[ldap:///] +
[ldap:///<searchbase>??<scope>?<filter1>] +
>> [??<scope>?<filter2>]"
>>
>> Assuming [ldap:///<searchbase>??<scope>?<filter1>]
returns a DN, this
>> works. However, if
[ldap:///<searchbase>??<scope>?<filter1>] returns no
>> entries, this value is NULL. Therefore, the rest of the set becomes:
>> "[ldap:///] + {NULL} + [??<scope>?<filter2>]"
>> ...which is handed to the '+' operation in slap_set_join, to become:
>> [ldap:///??<scope>?<filter2>]
>> ...which obviously isn't valid.
>
> Well, it is valid: it's an URI with an EMPTY DN.
In terms of LDAP, yes, but it can cause security issues here, as the EMPTY
DN is at a higher level that any one which would have been returned by a
normal result.
>> The attached patch changes the last case of the current behaviour for
>> slap_set_join on the '+' operation. This was already the behaviour
>> before version 1.24.2.6 Thu Sep 13 20:43:29 2007 UTC:
>> - {"One", "Two"} + {NULL} ==> {NULL}
>
> This is different from the above behavior, although it makes sense on
> its own. Probably we need two different addition operators: one
> inclusive (NULL is equivalent to "") and one exclusive (NULL nullifies
> the concatenation).
>
> Comments?
No problem in having the two operators. I just think the normal behavior
is to return NULL, has in term of sets the cartesian product A x NULL
returns NULL, not A.
Regards,
Raphael Ouazana.