Re: IE6 vs IE& vs IE8 on SBS
- From: "Larry Struckmeyer [SBS MVP]" <lstruckmeyer@xxxxxxxxxxxxxxx>
- Date: Wed, 3 Jun 2009 10:21:22 -0400
Hmmm:
I once asked (in a MS private group IIRC), why IE was so much quicker to
load than Firefox. The answer I was given was that IE had many of its bits
preloaded by the OS at startup. If true, this makes me wonder if there
isn't some of the aforementioned security problems present in any OS that
has IE6 or earlier installed, active or not. As I understand most of the
security problems with IE6 and earlier, they involved "especially crafted"
urls or packets that were to be explicitly downloaded by the human on the
other side of the mouse, but I suspect that a targeted attack, such as Code
Red, might be able to find those vulnerable IE6 or earlier dlls and upset
the apple cart.
I am not saying there is, I am only wondering out loud, and debating with
myself. If the primary reason to replace IE6 with IE7 is security, would a
system, server or not, be "more secure" if the preloaded bits were IE7 bits
instead of IE6 bits?
--
Larry Struckmeyer
Get your SBS Health Check
at www.sbsbpa.com
"Cliff Galiher" <cgaliher@xxxxxxxxx> wrote in message
news:et8uQX94JHA.5048@xxxxxxxxxxxxxxxxxxxxxxx
I agree with Cris and Russ, but I'll go as far as to say that you should
have a compelling reason to put IE7 on the server. Supported? Sure. Any
solid reason *not* to go with IE7? Nope. But I tend to always ask the
inverse of any question like this: Is there a solid reason *to* upgrade?
What do I gain?
With *any* upgrade, no matter how trivial, dll's get replaced and odd
things *can* crop up. I've seen where an app that relies on IE's activeX
engine stops working after a browser update. Anybody that has seen an MMC
snap-in display no data or in ridiculously tiny print because someone
messed with the IE defaults knows what I'm talking about. Two seemingly
unrelated technologies had a dependency that caused unpredictable
behavior. So although IE7 has certainly been out long enough to avoid
most, if not all, of those issues, it *can* happen. I don't think that
classifies as a "solid" reason, but it is a reason. If, however, a newer
app needs IE7's engine to run, then I'd happily install it. I wouldn't
*avoid* installing it at the expense of losing an app.
On the flipside, if no app needs it, then why upgrade? What do you gain?
Security?!? You really shouldn't be browsing from the server and you
should only be installing trusted 3rd party apps, so IE6, even with all of
its security woes, isn't a security hole on a server. It isn't being used
to browse and it isn't a listening service, hence it isn't a security
problem. You gain nothing by upgrading most of the time. So why do it?
Just food for thought,
-Cliff
"Joe#2" <Joe2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1248F096-80F1-497E-885D-FB0593FD6C38@xxxxxxxxxxxxxxxx
I have noticed in the past a lot of resistance to moving to IE 7 and IE 8
on
the server itself.
From a security standpoint it would seen that IE6 might be getting a
little
old. I also notice that WSUS want to push IE8 on the server.
Any solid reason not to go with IE7 or IE8 on SBS2003?
.
- Follow-Ups:
- Re: IE6 vs IE& vs IE8 on SBS
- From: Cliff Galiher
- Re: IE6 vs IE& vs IE8 on SBS
- From: Joe#2
- Re: IE6 vs IE& vs IE8 on SBS
- References:
- IE6 vs IE& vs IE8 on SBS
- From: Joe#2
- Re: IE6 vs IE& vs IE8 on SBS
- From: Cliff Galiher
- IE6 vs IE& vs IE8 on SBS
- Prev by Date: Re: Exchange logfiles is taking up space
- Next by Date: SMTP XXXX problem
- Previous by thread: Re: IE6 vs IE& vs IE8 on SBS
- Next by thread: Re: IE6 vs IE& vs IE8 on SBS
- Index(es):
Relevant Pages
|
