[Tickets #2563] NEW: ldap searches with * don't work after horde upgrade to 3.0.5

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2563
-----------------------------------------------------------------------
 Ticket             | 2563
 Created By         | colonel.flagg at hushmail.com
 Summary            | ldap searches with * don't work after horde upgrade to 3.0.5
 Queue              | Turba
 Version            | 2.0.3
 State              | Unconfirmed
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


colonel.flagg at hushmail.com (2005-09-06 04:27) wrote:

Upgrading from horde-3.0.4 to horde-3.0.5 seems to have
changed the behavior of ldap searches with a * in the search string.
3.0.5 replaces the * in the search string with the hex \2A.
colonel*flagg becomes colonel\2Aflagg.


WORKS: turba-h3-2.0.3 + horde-3.0.4

Aug 15 12:27:06 ldapserver slapd[25691]: [ID 902418 local4.debug]
conn=145864
op=2 SRCH base="o=example.com" scope=2
filter="(&(cn=*colonel*flagg*))"
Aug 15 12:27:06 ldapserver slapd[25691]: [ID 902418 local4.debug]
conn=145865
op=1 SRCH base="uid=cflagg,ou=People,o=example.com" scope=0
filter="(|(objectClass=top)(objectClass=person)(objectClass=organiza
tionalPerson)(objectClass=inetOrgPerson))"


BROKEN: turba-h3-2.0.3 + horde-3.0.5

Aug 15 12:26:42 ldapserver slapd[25691]: [ID 902418 local4.debug]
conn=145860
op=1 SRCH base="o=example.com" scope=2
filter="(&(cn=*colonel\2Aflagg*))"