Ede Wolf wrote:
>
>> Hi!
>>
>> I'd say: Get the proper app (eg. BabelPad on Windows, see attachment) and
>> then BASE64-encode the string.
>>
>> Regards,
>> Ulrich
>>
>
> Thanks, but windows is not an option. Again, base64 encoding is fine with
> echo -en "" | base64.
> With a browser I can search for the symbol and do copy paste into the ldif.
> All that works fine, even if my console font does not even support that
> symbol. I've
> done it. But feels a bit hackish.
>
> I just hoped, there was an option, to tell the server, when the ldif has this
> sequence, interpret it as an ecoding, not as a literal string.
> Now I know, this does only work for the dn (and maybe only openldap, will
> test, see other post), and for the rest I do have a work around.
>
The server doesn't do any reprocessing on the received strings. The escaping
was done by the client
(or libldap) when parsing your input. The server only processes UTF-8. You can
see this in the slapd
logs associated with the example ops I sent before:
63f4fd23.22d06a0c 0x7f1ceadfe640 conn=1004 op=1 do_add
63f4fd23.22d07cdf 0x7f1ceadfe640 ber_scanf fmt ({m) ber:
63f4fd23.22d08b9b 0x7f1ceadfe640 conn=1004 op=1 do_add: dn (cn=😀
face,ou=people,dc=example,dc=com)
The escaping is purely a client-side concern.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
