[turba] horde-3.0.4 upgrade to 3.0.5 breaks turba ldap searches with * in search string

[colonel.flagg@hushmail.com]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

This causes the ldap search to fail as shown below in the ldap logs.
Can anyone suggest a workaround for this or is it a bug?

Thanks

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*))"
Aug 15 12:27:06 ldapserver slapd[25691]: [ID 902418 local4.debug]
conn=145864
op=1 SRCH base="uid=cflagg,ou=People,o=example.com" scope=0
filter="(|(objectClass=top)(objectClass=person)(objectClass=organiza
tionalPerson)(objectClass=inetOrgPerson))"
-----BEGIN PGP SIGNATURE-----
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 2.4

wkYEARECAAYFAkMTr6EACgkQoSLP26XxZk9xrQCfWJ4NCqVyA4dAuErbWpuJAa3SlBsA
n3Dqbv5mQwYRnRWTPE/ZPRrfKjSG
=WFSi
-----END PGP SIGNATURE-----




Concerned about your privacy? Follow this link to get
secure FREE email: http://www.hushmail.com/?l=2

Free, ultra-private instant messaging with Hush Messenger
http://www.hushmail.com/services-messenger?l=434

Promote security and make money with the Hushmail Affiliate Program: 
http://www.hushmail.com/about-affiliate?l=427