Closed Bug 84298 Opened 25 years ago Closed 7 years ago

Server side sorting with sorting order creates wrong PDU

Categories

(Directory Graveyard :: LDAP Java SDK, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: uwe.krueger, Assigned: erhyuan)

Details

We use LDAP JAVA SDK 4.1 The following PDU was sent if I use "reverse order = true" when creating the LDAPSortKey (2 parameter constructor). PDUs controls_V3 = ARRAY OF 1 { ELEM[0] = STRUCT LDAP_Ctrl_V3 { bit_mask = 0xc0 ; controlType = 22 char value(s) 0000 31 2e 32 2e 38 34 30 2e 31 31 33 35 1.2.840.1135 000C 35 36 2e 31 2e 34 2e 34 37 33 56.1.4.473.. critity = FALSE ; controlVal_V3 = 21 char value(s) 0000 30 13 30 11 04 0b 64 65 73 63 72 69 0.0...descri 000C 70 74 69 6f 6e 81 02 00 81 ption....... } } decoded controlVal_V3: 1 T=30 - class = UNIVERSAL : constructed : tag = SEQUENCE { L=13 - 19 2 T=30 - class = UNIVERSAL : constructed : tag = SEQUENCE { L=11 - 17 T=04 - class = UNIVERSAL : primitive : tag = OCTETSTRING L=0b - 11 V=64 65 73 63 72 69 70 74 69 6f 6e T=81 - class = CONTEXT SPECIFIC : primitive : tag = [1] L=02 - 2 <<< ERROR V=00 81 <<< ERROR 2 } 1 } The Error was within the last 3 bytes (BOOLEAN) This BOOLEAN was coded 2 Bytes long. It's a wrong BER BOOLEAN coding! According to the RFC the BOOLEAN value has to be coded with the least possible length which was 1 Byte in this case. a valid ending were: T=81 - class = CONTEXT SPECIFIC : primitive : tag = [1] L=01 - 1 V=ff regards Uwe Krueger
QA Contact: __UNKNOWN__
Reassigned to Miodrag (Java LDAP SDK lead engineer). Please post a patch if you have one.
Assignee: mcs → miodrag
By the way, which directory server was used to expose the bug?
Status: NEW → ASSIGNED
@ Mark: Sorry - no patch available here @ Miodrag: Directory Server = Siemens DirX 6.0
Reassign LDAP JDK bugs owned by Miodrag (miodrag@formerly-netscape.com.tld) to E-Y (erhyuan@pacbell.net)
Assignee: miodrag → erhyuan
Status: ASSIGNED → NEW
Not activity for at least 6 years, closing.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.