IE 0-Day Flaw Used In Chinese Attack
bheer writes "A zero-day attack on IE was used to carry out the cyber attack on Google and others that's been getting so much ink recently, reports The Register, quoting McAfee's CTO. While the web (and security) community has pointed out the problems with IE's many security flaws (and its sluggish update cycle) in the past, IE shows no sign of vanishing from the corporate landscape."
Firefox breaks on some of the things I've had to work with. Just having it installed can cause them to not work correctly also.
-]Phreak Out[-
Right! And those folks are commonly known affectionatley here on Slashdot as Windows users. Just who do you think is responsible for the fact that the average computer user has no clue about security, and thinks everything "just works" if it isn't Microsoft?
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
Internal sandboxes don't protect you from having the compromised instance of IE being used to log passwords and steal other local information, nor does it prevent the compromised instance of IE from being a botnet node during the current session. Also, since IE still has to save files, load and execute programs, and so on, the strongest sandbox they can create is a leaky condom.
And security is like sex, once you're penetrated you're f***ed.
What a droll thing to say! Would you mind sharing with us where exactly you heard that? The FA just ruled Adobe out on this occasion. What is your motivation for pointing the finger at Adobe? The FA says IE is to blame. Somehow you know more than Google about this? Your conclusion, "Keeping Acrobat Reader fully patched and keeping your users alert and well-trained would probably stop a lot of it, but not all." completely misses the point. The problem was IE. I would like to know what idiot modded you insightful. The most obvious conclusion we could draw is to stay away from IE - at least until it is fixed.
Don't confuse the lack of an efficient and effective workflow with bad componentry. There are plenty of good packages to be had that can handle the various issues described in PP. If the developer doesn't know how to glue them together... well, it is a poor craftsman who blames his tools.
Of course if for some reason the freely available packages cannot be used then you are stuck trying to reinvent the wheel. Which I suppose is the case for Microsoft since it cannot use FOSS, and is also committed to supporting its legacy of strategically bad design decisions. Like folding the browser into the operating system.
Good browsers are not that difficult to work with. Firefox, Konqueror, Opera, and so on keep churning out steadily improving products in short order and have had very little trouble with security flaws. One of the reasons for this is that the black hats are well aware that any vulnerability they might exploit is likely to be short-lived, while if they just focus on MSIE, they are likely to get a much longer window of opportunity before the holes are patched.
Will
Yes, browsers are complicated.
But when you are using a browser while running with
admin privileges, and a non-trustable ActiveX-ploit,
you are begging to be taken advantage of.
You are being MICROattacked, from various angles, in a SOFT manner.
"Let's see. Using a monopoly position in search to disrupt the web browser market which they also participate in. Methinks not."
Not if everyone moves to Firefox (a COMPETITOR of Google) instead of Google's Chrome.
That is exactly my point. The VAST majority of people switching would go to Firefox, NOT Chrome.
Therein lies the pure GENIUS of this idea. Built-in anti-trust protection.
Even if a suit was brought against them, and they lost, what would be the mandated fix? Support IE again? By the time that dragged through the courts, the loss of IE users to Firefox would already have happened. Once you leave IE (for anything!), you never go back.