Re: Bug In RfcFilter.java prohibits escaped filters (ITS#2500)

[Kurt@OpenLDAP.org]

Closed.  Kurt

At 03:33 PM 5/13/2003, you wrote:


>A patch has been applied to fix this problem.  Thank you
>for bringing this to our attention.
>
>Please close the ITS
>
>-Steve
>
>
>>>> <will.wood@transamerica.com> 08-May-03 12:53:40 PM >>>
>Full_Name: Will Wood
>Version: 2.1.17
>OS: Windows
>URL: ftp://ftp.openldap.org/incoming/ 
>Submission from: (NULL) (162.123.17.80)
>
>
>There's a bug in RfcFilter.java in JLDAP
>(com/novell/ldap/rfc2251/RfcFilter.java) 
>that prohibits an escaped search filter from being properly addressed. 
>This is
>in the latest CVS drop.
>
>in unescapeString, a variable temp is being declared and initialized
>for each
>escaped hex digit, therefore the high order bits are always being
>chucked. 
>Solution move the
>declaration outside of the for loop and re-initialize when the escape
>character
>is hit.  I've also reported this bug to Novell as well, however I'm
>curious as
>to why
>no JUnit test caught the failure of using escaped values?
>
>
>463a464
>>       char temp = 0;
>477d477
><                     char temp = 0;  // get the value of the excaped
>sequence
>490a491
>>             temp = 0;                        // wipe out any old
>bits.