>>> Ede Wolf schrieb am 22.02.2023 um 11:03 in
>>> Nachricht
<6ad6c4b7-3f7d-3e2b-b1bd-936bd6060...@nebelschwaden.de>:
>> It seems the backslash notation is not actually defined for LDIF.
>
> That indeed is a valuable hint, out of curiosity I will test, wether
> other ldap server implementation
>>> Ede Wolf schrieb am 21.02.2023 um 16:10 in
>>> Nachricht
<5fed02ec-1e12-5264-305f-a3f69a335...@nebelschwaden.de>:
>> The same way you would enter Unicode in any other application. This is not
> an LDAP- or LDIF-specific question.
>>
>> 1) use a terminal and locale that support UTF-8.
>> 2)
Am 22.02.23 um 11:28 schrieb Howard Chu:
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:
Howard Chu wrote:
> 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 "" | base
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 sea
It seems the backslash notation is not actually defined for LDIF.
That indeed is a valuable hint, out of curiosity I will test, wether
other ldap server implementations will also accept at least the \FF
notation for the dn, but that is off topic here.
RFC 2849 (LDAP Data Interchange For
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 t
Ondřej Kuzník wrote:
> On Tue, Feb 21, 2023 at 05:32:01PM +0100, Ede Wolf wrote:
>> Hello Ondřej,
>>
>> Thanks very much! That is exactly the anwer I have been looking for - even
>> more so in fact, as additionally I have been educated, that the dn is a
>> different part from the rest of the ldif.
On Tue, Feb 21, 2023 at 05:32:01PM +0100, Ede Wolf wrote:
> Hello Ondřej,
>
> Thanks very much! That is exactly the anwer I have been looking for - even
> more so in fact, as additionally I have been educated, that the dn is a
> different part from the rest of the ldif. Makes sense, but I've never
Hi Ede,
in a search filter you are dealing with RFC 4515 which describes how to
escape values into that string, similar with URIs, which have their own
escaping rules you can leverage for this. With LDIF, you are dealing
with RFC 2849 which has no concept of escaping values: you can enter a
val
On Tue, Feb 21, 2023 at 04:10:53PM +0100, Ede Wolf wrote:
>> The same way you would enter Unicode in any other application. This
>> is not an LDAP- or LDIF-specific question.
>>
>> 1) use a terminal and locale that support UTF-8.
>> 2) use whatever tools your OS provides for entering Unicode
>> ch
The same way you would enter Unicode in any other application. This is not an
LDAP- or LDIF-specific question.
1) use a terminal and locale that support UTF-8.
2) use whatever tools your OS provides for entering Unicode characters. Probably
something named "Unicode character map" or similar.
Ede Wolf wrote:
> Am 20.02.23 um 18:06 schrieb Howard Chu:
>> Ede Wolf wrote:
>>> Hello,
>>>
>>> This is probably more a ldif than an OpenLDAP question, but still, maybe
>>> somebody knows the answer: Is there a way to put multibyte characters into
>>> an attribute
>>> value and let the server kn
Am 20.02.23 um 16:18 schrieb Ulrich Windl:
Hi!
Ever notices the "double-colons" "::"?
For example:
userPassword:: e1NTSEF9...
Kind regards,
Ulrich Windl
Yes, but I am unaware, that those hint to something else than base64
encoding? I may stand more than happily corrected, tough
My quest
Am 20.02.23 um 18:06 schrieb Howard Chu:
Ede Wolf wrote:
Hello,
This is probably more a ldif than an OpenLDAP question, but still, maybe
somebody knows the answer: Is there a way to put multibyte characters into an
attribute
value and let the server know, these are not to be treated literally
Ede Wolf wrote:
> Hello,
>
> This is probably more a ldif than an OpenLDAP question, but still, maybe
> somebody knows the answer: Is there a way to put multibyte characters into an
> attribute
> value and let the server know, these are not to be treated literally, but are
> utf8 character enco
Hello,
This is probably more a ldif than an OpenLDAP question, but still, maybe
somebody knows the answer: Is there a way to put multibyte characters
into an attribute value and let the server know, these are not to be
treated literally, but are utf8 character encodings?
I've tried to dig in
17 matches
Mail list logo
