![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
They can't win, can they?
Apr. 11th, 2003 02:04 pmOne of the hardware sites I frequent, [H]ardOCP, has the following newsbit up today:
Microsoft Server 2003:
This was particularly funny. Bruce Hembree got this message after a fresh install of MS Server 2003. Here is what Bruce said:
Hey guys. Here is the image of Microsoft Server 2003 blocking access to the unsafe features found on www.microsoft.com. This message is from a fresh default install of Server2003 and this is the message you get from IE when you go to www.microsoft.com. Kinda funny that they don't trust their own site.
They can't win, can they? In order to bolster security, Microsoft has enhanced the IE security configuration in Windows Server 2003. Practically everything that could be remotely dangerous in blocked -- essentially, anything but HTML -- because it's a server OS; you shouldn't be using it to browse the web anyway. If the user wants to unblock everything on a site, they have that option.
By default, every site is blocked. If Microsoft made an exception for www.microsoft.com, we'd instead have the same people complaining "Microsoft has configured Windows Server 2003 to block code from being executed off the web -- except their code, of course! Microsoft's own site can run things on your computer without your being asked. See, they're trying to take over your system without your permission! They want to rule the world!"
Microsoft Server 2003:
This was particularly funny. Bruce Hembree got this message after a fresh install of MS Server 2003. Here is what Bruce said:
Hey guys. Here is the image of Microsoft Server 2003 blocking access to the unsafe features found on www.microsoft.com. This message is from a fresh default install of Server2003 and this is the message you get from IE when you go to www.microsoft.com. Kinda funny that they don't trust their own site.
They can't win, can they? In order to bolster security, Microsoft has enhanced the IE security configuration in Windows Server 2003. Practically everything that could be remotely dangerous in blocked -- essentially, anything but HTML -- because it's a server OS; you shouldn't be using it to browse the web anyway. If the user wants to unblock everything on a site, they have that option.
By default, every site is blocked. If Microsoft made an exception for www.microsoft.com, we'd instead have the same people complaining "Microsoft has configured Windows Server 2003 to block code from being executed off the web -- except their code, of course! Microsoft's own site can run things on your computer without your being asked. See, they're trying to take over your system without your permission! They want to rule the world!"
