Re: Support for Base64 encoded values

["Trent W. Buck" <twb-nss-pam-ldapd-users [at] cyber.com.au>]

Arthur de Jong wrote:
> In theory it could be possible to do unicode normalisation in nslcd
> before passing strings in search filters to LDAP (patches welcome) but
> it would likely not solve all the problems.

That might backfire if different LDAP servers use different normal forms.
I've seen similar issues with filename normalization between OS X and GNU/Linux.

    References:
    https://en.wikipedia.org/wiki/Unicode_normalization#Normal_forms
    http://www.unicode.org/reports/tr15/

Hmm, it looks like this is already a solved problem for LDAP?

    http://www.unicode.org/L2/L2006/06347-ldap-info.txt
    → RFC 4518
    →  The input string is to be normalized to Unicode Form KC
       (compatibility composed) as described in [UAX15].  The output is the
       normalized string.

I don't understand LDAP RFCs very well.
Does that mean an RFC4518-conformant LDAP *server* will handle everything, and
nslcd's current behaviour is correct?
-- 
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
https://lists.arthurdejong.org/nss-pam-ldapd-users/