From: SourceForge.net <no...@so...> - 2005-07-20 11:59:06
|
Bugs item #1239915, was opened at 2005-07-17 22:26 Message generated for change (Comment added) made by mic42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112883&aid=1239915&group_id=12883 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: ldap Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Pierre David (pdav) Assigned to: Jochen Loewer (loewerj) Summary: Bad processing of "*" in ldap::search Initial Comment: The ldap::search processing of substrings does not handle "*" when used in more complex situations than "*x", "*x*" or "x*". For example, this little test program displays : (sn=david) : 3 result(s) (sn=da*id) : 0 result(s) <--- obviousely wrong! ------------------------------------------------------------------------ #!/usr/local/bin/tclsh8.4 package require ldap set host ldap.u-strasbg.fr set base "o=ulp" set filter1 "(sn=david)" set filter2 "(sn=da*id)" set ldapfd [::ldap::connect $host] set r1 [::ldap::search $ldapfd $base $filter1 {}] set r2 [::ldap::search $ldapfd $base $filter2 {}] ::ldap::disconnect $ldapfd puts "$filter1 : [llength $r1] result(s)" puts "$filter2 : [llength $r2] result(s)" -------------------------------------------------------------------------- The attached patch provides a general solution to the "*" handling. It is still not the complete solution to RFC 2254, but a little step forward. .. :-( ---------------------------------------------------------------------- >Comment By: Michael Schlenker (mic42) Date: 2005-07-20 13:59 Message: Logged In: YES user_id=302287 Patch is now commited in CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112883&aid=1239915&group_id=12883 |