From: Graham B. <gb...@po...> - 2001-03-08 11:23:18
|
On Thu, Mar 08, 2001 at 11:04:06AM -0000, Chris Ridd wrote: > Let's see, what canonicalisation does canonical_dn do.. > > * it lowercases values that are # followed by hex, > * it lowercases types that start with an OID, > * it backslashifies RFC 2253-magic characters, > * it backslash and hex encodes 0x00-0x1f and 0x7f-0xff characters, > * it surrounds values with leading/trailing/multiple spaces with quotes. > > (Actually, that last part is not permitted by RFC 2253. You should replace > those spaces with "\20" or "\ ". I suspect "\20" would be safer especially > at the end of a string, to avoid someone simply ripping trailing spaces off > and leaving the string ending with a dangling slash.) 2253 also no longer requires the escaping of multiple spaces within a value. > Those canonicalisations look OK to me. Have I missed any others? canonical_dn also reorders the parts of multi-part RDNs Graham. |