Issue #121 has been updated by Thomas Chemineau.
I pasted an extract from the RFC 2253 (http://www.ietf.org/rfc/rfc2253.txt) which is obsolete in fact. I seems that the RFC 4514 is the latest: http://tools.ietf.org/html/rfc4514. It is almost the same, apparently. ---------------------------------------- Feature #121: [sync] function to escape special characters in RDN http://tools.lsc-project.org/issues/show/121 Author: Thomas Chemineau Status: New Priority: Normal Assigned to: Category: Core Target version: RFC say: 8<-------- If the UTF-8 string does not have any of the following characters which need escaping, then that string can be used as the string representation of the value. o a space or "#" character occurring at the beginning of the string o a space character occurring at the end of the string o one of the characters ",", "+", """, "\", "<", ">" or ";" Implementations MAY escape other characters. If a character to be escaped is one of the list shown above, then it is prefixed by a backslash ('\' ASCII 92). Otherwise the character to be escaped is replaced by a backslash and two hex digits, which form a single byte in the code of the character. 8<-------- It could be useful, when we build our one DN, to have a function that verify and escape special characters in the RDN value, as mentioned above. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lsc-project.org/pipermail/lsc-dev/attachments/20091009/1fb919f2/attachment.htm>
