Well, since you failed to click on the link Josh3io provided four words into his original post, you can go to http://www.trillian.cc

This app has been getting a lot of notice lately not only for its integration of multiple IM systems but also for the way it implements its "skins" via XML. Very slick.

 

Is someone a little cranky today???

 

No, just that my attention spans at least five words and I thought I was at the low end of the scale.

For those that care, AOL will be implementing a server-side fix that does not require an client change. For more information click here or (for those of you that have already nodded off......) http://news.cnet.com/news/0-1005-200-83475....html?tag=mn_hd

 

Damn. My company just shut down all usage of AIM this morning. They followed up with a global voice message summarizing the article you just posted. I feel kinda lost without my AIM.

 

[QUOTE]Originally posted by rolotomasu
[B]Damn.

 

thanks gregg

 

Can anyone tell me if this is a related issue?

http://members.ozemail.com.au/~geoffch/security/aim/

 

different.

 

A server-side fix does nothing to prevent a malicious programmer from attacking clients directly, bypassing the central server. The buffer overflow is in the client and that is where AOL needs to get their asses in gear to fix the problem.

 

Not that I have't said this enough...

AOL Sucks!