You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Hard to say, log in with an affected ICQ number, doesn't happen with all
2. Watch as you are denied login. =D
What is the expected output? What do you see instead?
Would expect to be logged in but am denied.
What version of the product are you using? On what operating system?
Latest SVN on Linux, Mac OS X, Windows, etc.
Please provide any additional information below.
While trying to debug this error code, I found out the following... (this
is what I posted on the adium x tracker, http://trac.adiumx.com/ticket/4582)
Hey folk, I noticed this:
Go back to using the insecure xor-based authentication for ICQ because
I think some people's ICQ numbers will trigger problems when using MD5.
Namely login error code 0x000c and error url
http://www.aim.com/errors/INVALID_DB_FIELDS.html?ccode=us&lang=en
From libgaim:
http://fisheye1.cenqua.com/browse/gaim/gaim/src/protocols/oscar/auth.c
I haven't looked much at the actual code for joscar to submit a patch. I
didn't know if this would trigger an "oh crap, ok, fixed". If not, let me
know and I'll see what I can do about providing a patch.
Original issue reported on code.google.com by daniel%[email protected] on 7 Oct 2006 at 4:40
The text was updated successfully, but these errors were encountered:
Sorry for the late response. I tried implementing this XOR thing a month or two
ago,
and as I recall it didn't fix it for most accounts, and it broke other
accounts. If
you wanted to experiment with it you might get better results, I'm not very
familiar
with ICQ.
Original issue reported on code.google.com by
daniel%[email protected]
on 7 Oct 2006 at 4:40The text was updated successfully, but these errors were encountered: