Passwords must only contain ascii characters, as long as the charset
of the authentication method is undefined. This has nothing to do with
Horde.
Zitat von Stefan König <[email protected]>:
Correcting myself, the transmitted bytes 0xc4 and 0xe4 are OK. I got the
wrong table.
However, this changes nothing about the result of the IMAP server
rejecting the login.
If I login via telnet, everything works perfectly....
thanks again
regards
Stefan
Stefan König schrieb:
Hello List,
I have a slight problem with IMP (4.3.6) running on top of Horde 3 (3.3.6).
I use our IMAP server as an auth backend, which works like a charm.
Today I noticed, when I have a german special character
in the password, this character is not being forwarded to the
authentification backend correctly.
Example:
login: [email protected]
pass: 12tÄst34
then tcpdump shows me, that IMP tries to authenticate against the IMAP
server with password "12t.st34" where the wrong byte shows in tcpdump
as 0xc4 (decimal 196) where it should be 0x8f (dec. 142 in extended
ascii table).
The byte changes with the character, if I set "12täst34" as password,
the byte changes to 0xe4 (dec. 228).
I wonder why and how this happens. I checked the language settings in
Apache (2.2.10), everything seems to be correct.
Could someone point me into the right direction?
Thanks alot!
regards
Stefan
--
Jan Schneider
The Horde Project
http://www.horde.org/
--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
