Issue #55 has been updated by Anonymous.
Looks like the character encoding could be solved: "Windows uses little-endian UCS-2 as the character set" from http://www.eyrie.org/~eagle/journal/2007-07/010.html ---------------------------------------- Bug #55: AD password encoding doesn't support non-ASCII characters http://tools.lsc-project.org/issues/show/55 Author: Jonathan Clarke Status: New Priority: Normal Assigned to: Category: Core Target version: 1.1.1 Thomas found that if a password contains special characters (like "?", "?", etc.), LSC says that password modification succeed, we cannot authenticate with this new password. In fact, the old one is still valid :/ It may be a wrong charset used to encode the password. Default charset on Windows systems is CP1252. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lsc-project.org/pipermail/lsc-dev/attachments/20090602/b181376c/attachment.htm>
