Re[4]: [SOGo] Exception in processing of unicode strings
Dmitri Ivanov
sogo@opengroupware.org
Wed, 21 Nov 2007 21:27:50 +0300
By the way, i didn't mention: i get a lot of errors about unsupported
locale:Russian. Is that a critical error? I thought i can safely
ignore it...
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.
DI> I think, that is not a failure in auth module. Why?
DI> I presume it works in a standard way:
DI> 1.ldap_search filter=(samAccountName=<passed uid>) attr=DN
DI> 2.ldap_bind <dn, passed cleartext_passwd>
DI> 3.if (ldap_error == LDAP_SUCCESS) then authentication successful.
DI> On step 2, DN _may_ contain cyrillic characters inside it. I've tested
DI> this, placing a test user account into a cyrillic named org. unit.
DI> No error in that case.
DI> But afterwards, CN of that user is further processed. And here we get
DI> an exception when CN contains any cyrillic characters.
DI> --
DI> Best regards,
DI> Dmitri mailto:ivanov_dv@mediasign.ru
--
Best regards,
Dmitri mailto:ivanov_dv@mediasign.ru