Skip to main content

IE7 and how much it sucks

I wrote this article on i got lots of MS zealot feedback saying that I was bashing.

Thanks to one of our readers that wrote in to tell us that IE7, will be released this month via Automatic Update according to Microsoft's "IEBlog".

Unfortunately, it's still based on a similar code base, and will still hold the majority of market share. So, this brings me to the point of the article which I had originally intended..

My advice? Diversify. Use other browsers. I use Safari, Firefox, and Opera. I own zero Windows based computers, but I have access to thousands. I suggest you out there in 'reader land' switch to something else. Unless we see empirical evidence that IE7 is vastly more secure and superior.. it will wind up like its predecessors.

Yes, I know that on some corporate environments, its impossible to switch. There are applications that are dependent on IE. But I blame the Application Developers. Code to more open standards, try not to use ActiveX controls. Other browsers don't use them, and they work fine. I had a reader write in and say that in their environment (healthcare), they are dependent on IE. My wife works in healthcare, so I feel your pain. I know, I know, its unfortunate, sometimes corporate rollouts of all.. are not possible, however, give it a shot.

I used to work in an environment where IE was necessary for a couple of things. So, we used IE for those two things, and Firefox for the rest. My whole diary entry can be summed up in one line: "Where you don't HAVE to use IE, don't."

II have received alot of feedback since I wrote the initial article. Most people don't like the fact that I am saying that IE's security is lacking. It's fact. Everything has vulnerabilities. Every OS, every product, every browser. I have been cited, publicly stating that if Apple was 95% of market share and Microsoft was 5%, who is to say that the roles wouldn't be reversed. Hackers target the 70% of the browser market (IE) because that's the MAJORITY of what is out there. However, if the roles were reversed, who is to say that it wouldn't be backwards? Who is to say that there wouldn't be hundreds of thousands of vulnerabilities for Apple out there? Yes, I think that Apple is inherently more secure, (I use macs), but that's not to say that if the tables weren't turned we wouldn't have a different result.

In other Microsoft News:
Microsoft rewards Adware programmer with MVP status. Link here

Reader Dan writes in to tell us:
"You may also want to note that Firefox even has a plug-in available to open certain links in IE. This makes it even easier to follow your advice of only using IE when you absolutely must." --

Update #1
Mentioned native apps.

Update #2
Mentioned Feedback

Update #3
Clarifying the article for it's original intention: Diversification.

Update #4
Added MS MVP article

Updated #5
Added Firefox plugin


I still say I'm right.


Popular posts from this blog

Offset, Depth, Distance, and Within

Without going off the deep-end here and discussing every single Snort rule keyword, I just wanted to touch on a few modifiers that people sometimes misunderstand.  They aren't difficult, and hopefully after this explanation and a few examples, I can clear some of the air around these five modifiers.

The five modifiers that I am talking about are
OffsetDepthDistanceWithinnocaseThese five modifiers are not keywords of themselves, but rather they apply as modifiers to another keyword.  That keyword is "content". The content keyword is one of the easiest pieces of the Snort rules language as all it does is look for a particular string.  So for instance if I wanted to look for the word "joel" within a packet.  A simple:
content:"joel";Would allow me to do that.  The interesting part comes into play when you want to specify where inside of a particular packet you want the string "joel" to be looked for.  If you are running just a plain content ma…

Writing Snort Rules Correctly

Let me start off by saying I'm not bashing the writer of this article, and I'm trying not to be super critical.  I don't want to discourage this person from writing articles about Snort rules.  It's great when people in the Snort community step up and explain some simple things out there.  There are mistakes, it comes with the territory.  If you choose to be one of the people that tries to write Snort rules, you also choose to be someone who wants to learn how to do it better.  That's why I write this blog post, not to bash the writer, but to teach.

I noticed this post today over at the "Tao of Signature Writing" blog, and to be honest I glanced over most of it figuring it was a rehash of things I've already read or things that have already been written from countless people about "Here's how you write Snort rules!".  I scrolled down quickly skimming, not reading at all really, and noticed this part:
Now, let us look at the second questio…

Safari 5.1.4 now available

Safari 5.1.4 now available, fixes issues and improves performance | TUAW - The Unofficial Apple Weblog:

Improve JavaScript performanceImprove responsiveness when typing into the search field after changing network configurations or with an intermittent network connectionAddress an issue that could cause webpages to flash white when switching between Safari windowsAddress issues that prevented printing U.S. Postal Service shipping labels and embedded PDFsPreserve links in PDFs saved from webpagesFix an issue that could make Flash content appear incomplete after using gesture zoomingFix an issue that could cause the screen to dim while watching HTML5 videoImprove stability, compatibility and startup time when using extensionsAllow cookies set during regular browsing to be available after using Private BrowsingFix an issue that could cause some data to be left behind after pressing the "Remove All Website Data" button