[Pidgin] #1124: [XMPP] Passwords containing non-ascii characters does not work
Pidgin
trac at pidgin.im
Thu Sep 25 15:34:42 EDT 2008
#1124: [XMPP] Passwords containing non-ascii characters does not work
---------------------+------------------------------------------------------
Reporter: cartman | Owner: nwalp
Type: defect | Status: new
Milestone: | Component: XMPP
Version: 2.0 | Resolution:
Keywords: |
---------------------+------------------------------------------------------
Comment(by Morbii):
Sorry (I didn't even realize what XMPP was). It's an ICQ account, but I'm
not sure that it matters (or, it's the same bug with a different
provider). The problem seems to be with a non-ascii password - I have the
idneitcal problem described in this bug. I looked at accounts.xml and
verified that the password is definitely stored correctly (so the ctrl-
shift-u stuff was successful), but I'm continually denied being logged in.
I tried changing the encoding of the accounts.xml file as a longshot (it
did display visibly in notepad, but I was worried it might not read in
correctly) and it didn't work.
It might be helpful to mention that I am using the Windows version of
Pidgin.
Finally, as above, some important facts to mention.
- Pidgin will not let me into my ICQ account that uses non-ascii chars for
a password. All other accounts work beautifully (and non have non-ascii
chars). I have verified the password in accounts.xml
- ICQ 6 itself won't allow me to log in with my non-ascii password but ICQ
Lite will. The problem is that it forces me to immediately upgrade. In
ICQ6, even with auto-connect it will still fail if the password was saved
over from ICQ Lite. I can't change the password because the only way to
do that is to log into ICQ6.
- Trillian is the only IM client I can get to work with my ICQ password,
but even it does funky things. When you go to preferences, it
automatically tells you "your password will be updated when you restart"
and I immediately kill trillian. Using Spy++ it shows that the password
is missing the two non-ascii chars.
Given the first two points (stored correctly in accounts.xml; auto-login
saved from ICQ Lite still doesn't work in ICQ6), I suspect something about
the password transport to the ICQ servers. I don't know how this works at
all, but perhaps it has to do with XML encoding? Alternatively, it could
be that ICQ6 updated the saved password "database" and simply sanitized my
password to uselessness.
Thanks for replying.
--
Ticket URL: <http://developer.pidgin.im/ticket/1124#comment:12>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list