note
ghenry
<p>It actually comes from rfc2849:</p>
<p><b>The LDAP Data Interchange Format (LDIF) - Technical Specification</b>:</p>
<p><pre>
4) Any dn or rdn that contains characters other than those
defined as "SAFE-UTF8-CHAR", or begins with a character other
than those defined as "SAFE-INIT-UTF8-CHAR", above, MUST be
base-64 encoded. Other values MAY be base-64 encoded. Any
value that contains characters other than those defined as
"SAFE-CHAR", or begins with a character other than those
defined as "SAFE-INIT-CHAR", above, MUST be base-64 encoded.
Other values MAY be base-64 encoded.</pre></p>
<p>So since we have <pre>{crypt}</pre>the<pre>{</pre> triggers the base64 encoding if you slapcat the Directory data out into LDIF. it has nothing to do with whom or what added the {crypt} data to the directory in the first place.</p>
<div class="pmsig"><div class="pmsig-386673">
<small>Walking the road to enlightenment... I found a penguin and a camel on the way.....<br/>
Fancy a yourname@perl.me.uk? Just ask!!!</small>
</div></div>
683676
684610