[ http://issues.apache.org/jira/brows...242
4445 ]

Emmanuel Lecharny commented on DIRSERVER-634:
---------------------------------------------

Ok, this is my fault.

The ASN.1 BER decoder analyze the DN and try to parse the DN. If it does fai
l, the it throw a DecoderException, which leads to a protocol error.

This is really bad, and this will happen almost everywhere we have a DN in a
 request. An INVALID_DN_SYNTAX must be thrown instead.

> Delete with illegal DN causes client to hang
> --------------------------------------------
>
>                 Key: DIRSERVER-634
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-634
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0-RC3
>         Environment: Sun ONE Directory SDK for Java 4.1
> ApacheDS 1.0 RC 3
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Microsoft Windows XP version 5.1 Service Pack 1
>            Reporter: Stefan Zoerner
>         Attachments: DeletionWithIllegalNameTest.java, DIRSERVER-634.ldif,
 DIRSERVER-634.log
>
>
> A delete operation with an invalid DN causes the client to hang. The expected resu
lt is LDAP error code 34 (INVALID_DN_SYNTAX) (preferred), or 32 (NO_SUCH_OBJECT). Fo
r instance I tried to delete DN "This is an illegal name,dc=example,dc=com" (no attr
ibu
te name in RDN).
> Unfortunately, I was not able to create this situation with JNDI. Its LDAP Provide
r seems to ignore such an operation, there is no Exception at all. A Java test case 
created with Sun ONE Directory SDK for Java caused the client to hang, and does not 
pro
duce the result code expected. I'll attach it to this issue.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://iss
ues.apache.org/ji...nistrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]