there are about 10 more sploits that work with the new 1900 build. If you pople were smart ud look throught ur html book and find some of those magical codes he he. the other code was &#.770; or 79 both workwiht out the periods

the string is "̂" without the quotation marks

the html messed it up, its "&.#.7.7.0.;." without the quotation marks or the periods.

Do you people realize how old this expliot is? The public finds out about stuff a long a** time after it first occurs and here is another example. ::sigh:: And it's not betanews's fault because they never said the string, someone else did!

They did too. The original article had the string, but they apparently have edited it out.

What is the actual line? I know it was something to the effect of #&...; Please email it to spyrl69@hotmail.com I have a friend who is to stuborn to upgrade and I am hoping this will make him do it.

haha, jeez you had to be a news site to figure out that little "bug". This has only been going on for uhmmm 3 years? since AIM first came out? Cmon betanews, dont be dumb.

Thats like saying there is like reporting on a bug where you can crash any version of apache (although not nearly as serious) and giving everyone an exploit made by you all and telling them to go use it on everyone the can, how stupid. You all do relize you could be held reliable for any damages, what if some numbnut goes around iming random people with that, and one person happens to be working on a $50,000 report for his business and his comp crashes because of some little bug you all had to give out to everyone and his grandmother (hi grandma). Anyway, to put it bluntly this was totally un-professional and completely unneeded, all you had to do is say that there was a bug in AIM and to update.

My $0.02

betanews guys are fairly Anti-MS too...why else do you think they try to list as much negative items they can and bring up past bugs, and couldn't wait to jump on the 60,000+ bugs bandwagon. Any responsible reporting crew wouldn't have even bothered mentioning it.

It doesn't crash the system, just AIM.

Actually it's very proffesional of them to post this. Do you think that security through obscurity is the way to go? If your going to use an OS that is full of holes and about as sucure as a piece of swiss cheese then you SHOULD be interested in learning about updaets to fix the holes. If you think that living with your head in the sand and pretending that Windows is just swell then you will get what you deserve.

Lets face it most windwso apps are buggy because Microsoft has lowered the standard for software quality. I would suggest making the move to Free BSD if you want a secure OS.

Well, they didn't exactly mention what the html tag is. So all people know to do is to d/l the newer version

IT's not eFront's software. It's AOL's. AOL are the unprofessional ones. If AOL had bothered to test their software, rather than spend their time trying to block legitimate access to their IM servers throught protocols they published, you wouldn't be in this mess in the first place.

If you were to sue somebody if your computer died, it would have to be AOL. NOT eFront.

My aren't we just the optimist? I think that bug announcement is meant more for herding the users of AIM to upgrade their stuff. Nowhere in the article did it say what the code is or where to find it.

the e-front people announce all the m/s bugs because a good chunk(I'd guess 90%+) of software are released for it. IF everyone released all their software for Linux or BeOS 5, there'd be bug announcements left and right for them. You can't blame an OS' instability on poorly coded apps.

p.s.
I am as anti microsoft as all those fanataics, but, I also run Win2k, and it is damn stable.

but not quite. Most diehard Windows users mess around with other operating systems just, but we don't go around bashing other OS'es for their shortcomings(unless anti-MS idiots start spouting bogus claims for their OS'es). When you try to say MS products have security holes and what not...you are just admitting to being less than capable. Learn to use software and stop crying. If you aren't a kid, stop being such a kid with all this. And if in fact you are, then keep on whining.

Actually they did, but then revised the article with it out.

That is an un-educated statement. With the execptions of games and dvds, which are just starting to be tapped by the *nix market, there isn't a single thing you can do on your windows box that I can't do on my *nix box. That being said security and stability to *nix users and the Windows users are very different things. Stability to Windows users is having to reboot your machine once every couple of days. Stability to *nix users is having to reboot your machine once every year. Security to a Windows user is "See it makes you login before doing anything." Security to a *nix user is "Hey look they can't login, and they can't crash my machine remotely either." If you don't believe me go read a reputable security site (CERT, SecurityFocus, etc.) and see what they have to say. I'm quite certain you will find many more exploits for Windows than for most *nixes.

Sue? Its beta software. If it trashses your HD, too bad.

hmmmm, let's think. if you had read what was actually going on, you would have seen that the article says that NEWER versions (i.e. BETAs, or possibly even non beta's) can crash the older versions (that is ANY version, including the non-beta ones). SO, hapless users who were mindung their own business and using an older version (such as 3.0, 2.0, etc) could have their aim clients crashed by the newer clients. The people whose computers were being crashed were not nesecerily using a beta. This means that AOL was at fault for not protecting them. These users were using a program that AOL claimed was safe! I fight the fight against ignorance and injustice. Thank you.

that is old news. it was discovered like a month ago.

I'm l33t now.

It works..... Tried on 6 people...... which worked on 4 people..... other 2 had newer version.=d

what's the string? ])