Starting today (4/27) when I try to sign on I get a "unknown signon error." I am getting the same error with TIK and TAC, so I imagine the AOL folks have changed their protocol, but I'm counting on you to work around it.
Anyway, do you know what's going on here?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have not had this problem today or any other day with gaim. I spoke with other developers too and no one else has had this problem.
Anyone who has worked on the faim libraries: Is this sort of problem possible? Is it a feasible problem that AOL could lock out "rogue" clients written by little hacker punks like us?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
isn't that how aol fought back against microsoft's messenger? iirc, they looked for bugs in their implementation of toc which microsoft's client didn't have, and rejected authentication requests that lacked those bugs. so yes, i think it's possible for them to lock out gaim users, but for them to fight against a free, opensource project would probably garner more bad publicity than they'd like.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
MSN didn't use the "open" TOC protocol, they used AIM's own OSCAR protocol
which pissed AOL off to no end. AOL responded by exploiting an "accidental" buffer
overrun in *ALL* AOL AIM (OSCAR!) clients that caused them to send a packet back
to the AIM server containing part of the EXE. Any client that didn't repond got kicked off.
No, gaim doesn't have anything to worry about. MSN's fate was partly because they
used OSCAR, and partly because AOL doesn't like the Evil Empire.
So how about that file transfer? :)
Ben
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Starting today (4/27) when I try to sign on I get a "unknown signon error." I am getting the same error with TIK and TAC, so I imagine the AOL folks have changed their protocol, but I'm counting on you to work around it.
Anyway, do you know what's going on here?
I have not had this problem today or any other day with gaim. I spoke with other developers too and no one else has had this problem.
Anyone who has worked on the faim libraries: Is this sort of problem possible? Is it a feasible problem that AOL could lock out "rogue" clients written by little hacker punks like us?
isn't that how aol fought back against microsoft's messenger? iirc, they looked for bugs in their implementation of toc which microsoft's client didn't have, and rejected authentication requests that lacked those bugs. so yes, i think it's possible for them to lock out gaim users, but for them to fight against a free, opensource project would probably garner more bad publicity than they'd like.
MSN didn't use the "open" TOC protocol, they used AIM's own OSCAR protocol
which pissed AOL off to no end. AOL responded by exploiting an "accidental" buffer
overrun in *ALL* AOL AIM (OSCAR!) clients that caused them to send a packet back
to the AIM server containing part of the EXE. Any client that didn't repond got kicked off.
No, gaim doesn't have anything to worry about. MSN's fate was partly because they
used OSCAR, and partly because AOL doesn't like the Evil Empire.
So how about that file transfer? :)
Ben
AOL's TOC authentification server barfed for about 3 or 4 hours yesterday. No biggy, all is well now.