Login Register
Watch: New Yorkers March For Trump in the Bronx Ahead of Rally --- --- Former CDC Director Redfield Admits ‘Significant Side Effects’ From COVID-19 Vaccine --- --- Underage Girl Trafficked Over Border Rescued In California After Months of Sex Abuse --- --- Israeli President ‘Lied About Shani Louk Being Beheaded by Hamas’; ‘Complete’ Body Returned --- --- Helicopter Carrying Iranian President, Foreign Minister Crashes – Reports --- --- Slovak PM’s Condition ‘Remains Very Serious’ – Deputy --- --- Zelensky Blasts West for Wanting Conflict to End --- --- Lab-Grown Meat Banned in Second State: Alabama Follows Florida’s Lead --- --- European Commission Shuts Down Wilders’ Plan to Opt Out of EU Migration Pact --- --- NOTAM Sparks Confusion Over Possible Russian Hypersonic Missile Test Off California Coast --- --- US Issues Gay Events Terror-Attack Warning --- --- Vaping Linked to Earlier Onset of Asthma: New Study --- --- Illegal Immigrant Children Being Housed with Sex Offenders in Massachusetts --- --- Glyphosate Detected in Human Semen for the First Time at 4x Higher Concentrations than in the Blood --- --- Wearing Face Masks Did Nothing To Reduce Risk of Infection with COVID Omicron Variant: New Study --- ---



[Reply]
Forum Index > AIM/ICQ Discussion
Major fracture in AIM client support
Posted on: 12-24 6:27 pm
ohhihohello57

For a while I've had problems logging in on AIM 1.0 due to the server not accepting the roast/XOR-based authentication it used, despite it working before. But as I tested more of the early clients, I realized that they don't work in one way or another. I tested (almost) all of these clients on a Windows 2000 VM and my host machine (Windows 7). These were the results:

- AIM 1.0: Doesn't install on 64-bit systems; errors out on login with "Unknown error"

- AIM 2.1: Stays at Step 2 (authentication) and does nothing

- AIM 3.0: Errors out with a "server disconnected" message

- AIM 3.5: Same situation with 2.1; when sniffing the packets sent to and from this application, it's clear that it uses MD5 authentication and authenticates successfully, but when it is introduced a BOS server (on port 5191), it doesn't attempt to connect to it

- AIM 4.7: Crashes when it reaches Step 2

Anything on or after 4.8 successfully logs in and fetches your buddy list.

I have a problem with this as these versions did work at one point, and they're also still available for download on this very site. The sudden halt of support for these clients is frustrating for people who use these affected versions or plan to and can't get to login, thinking that it's some sort of cruel joke. I suggest iWarg to get to the bottom of this problem ASAP to avoid any further complications in the future and to make sure he offers what he advertises (again, the downloads page).

~ ohhihohello57

if (Nerd->Personality == (NERD_PERSON_FRONTFACING + NERD_PERSON_SMARTALEC)) { return; }
Posted on: 12-24 7:08 pm
ohhihohello57

I'd also like to bring up that reformatting your screen name and updating your email address only works on 5.1+, while it doesn't work on 4.8, and changing your password in your AIM session (4.8) does nothing at all. I'd understand not implementing in-session password changing (it's sent as cleartext to the OSCAR server, last time I checked), but the rest isn't anything insane to get working on the older clients.

Also, for the later AIM clients that used links for account management, you might want to get to fixing that too, since it's all specified by the server. ;p

if (Nerd->Personality == (NERD_PERSON_FRONTFACING + NERD_PERSON_SMARTALEC)) { return; }
Posted on: 12-25 4:24 pm
Wildman

Beta Tester

it would have been nice if someone pointed this out earlier.. since yeah that's not supposed to happen.

Hououin - your friendly neighborhood AIM server operator
< - 1 - >

[Reply]