Login Register
BREAKING: Major Update On The Minnesota Trans-Cult Killer’s Father Working At A High-Level For The CIA/NSA/DOD! --- --- Update: Trump’s Global Tariffs Ruled Illegal By Washington Appeals Court, But… --- --- Man Arrested for Making Bomb Threat at Dallas ICE Facility --- --- RFK Jr. Revokes Emergency Use Authorization For Covid Injections --- --- Thrice-Deported Child Sex Predator Caught Living at California Daycare Run by DACA-Recipient Wife --- --- Trump Scores Major Victory!!! The Democrat Governor Of Maryland & Other Blue City Leaders Are Now Admitting Trump Was Right When He Deployed National Guard To DC And The Crime Rate Plunged! --- --- GOOD VS. EVIL: World Awakens To Spiritual War As Democrats Publicly Attack People Praying For Victims Of Catholic School Trans Shooting! --- --- Trump Projects Republicans Will “WIN BIG IN THE MIDTERMS” --- --- Friday War Room LIVE: Learn Secrets Behind the Trans Catholic Church Shooter, PLUS The Trump Effect: The Good & The Bad, AND…Covid Makes A Comeback! TUNE IN & SHARE! --- --- Watch: Psychiatrist Says It’s Terrifying & Dangerous That So Many Americans Are On SSRIs --- ---



[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]