Re[3]: [SOGo] Exception in processing of unicode strings

[Dmitri Ivanov]

Hello Wolfgang,

WS> Anyway I will have a step-by-step look at the identification
WS> process. SOPE is full of calls to getCString which lacks in
WS> correctness when all your encodings are not the same between your
WS> web application and your server environment. Also, certain
WS> implementation in GNUstep used to be buggy.

I think, that is not a failure in auth module. Why?
I presume it works in a standard way:
1.ldap_search filter=(samAccountName=<passed uid>) attr=DN
2.ldap_bind <dn, passed cleartext_passwd>
3.if (ldap_error == LDAP_SUCCESS) then authentication successful.

On step 2, DN _may_ contain cyrillic characters inside it. I've tested
this, placing a test user account into a cyrillic named org. unit.
No error in that case.

But afterwards, CN of that user is further processed. And here we get
an exception when CN contains any cyrillic characters.

-- 
Best regards,
 Dmitri                            mailto:ivanov_dv@mediasign.ru