IE7 Leaked

lju writes "IE7 has been leaked according to pcpro. From the article: '...last Friday it was revealed that a build of the new browser - version 5299 - along with numerous screenshots, was available online.' "

Comments

Leaks? I'll show you LEAKS!

[Saeed al-Sahaf]

IE7 can't possibly leak as much as Firefox. That browser is a memory pig! But I guess that's the price for security and "standards compliance"

How can something publicly available be "leaked"

[kimvette]

Last I checked, MSIE 7 is available via MSDN subscriptions, Action Pack subscriptions, and even Microsoft's own web site . It's not like anyone outside of M$ has not seen MSIE 7.0 already. So a single build got leaked a little early -- this is a) nothing unusual and b) not anything significantly different from what was previously made available through legitimate. This strikes me as: "Oh boy, screenshots of a beta everyone has been able to download for months. Oh wait, this is DIFFERENT because the build number in help-> about is different."

Now if the SOURCE were leaked, that would actually be something newsworthy.

IE tied into the OS

[mindaktiviti]

I wonder how big and clunky Internet Explorer would be if it wasn't tied into the Operating System.

Re:Obligatory Troll...

[drinkypoo]

And of course when running as non-admin, all the security exploits are irrelavent.

This is such an ignorant statement. I hate seeing it, and I see it over and over again on slashdot.

First, it assumes that there are no local privilege escalation exploits. This is a poor assumption, especially on Windows, but really on any OS with privilege levels.

Second, it assumes that your personal data is not worth anything. Yours might not be, but mine is.

Third, it assumes that there isn't some way to muck with the system to get Administrator to run something when they log in. This is not a safe assumption either. Hell, there's still people running FAT32 on Windows XP. They have no protection.

Re:Obligatory Troll...

[Crazyscottie]

If look at the security hole listings for IE, there are exactly 3 buffer overflow problems found in the entire history of the browser.

Three documented buffer overflow problems. Keep in mind that Microsoft is well known for its lack of documentation in both bugs and operating system "features." Also remember that buffer overflows aren't the only kind of "non-stupid-user" vulnerability in any application (e.g. heap overflows).

And of course when running as non-admin, all the security exploits are irrelavent.

Disregarding the fact that "irrelavent" is not an English word, how many Windows users do you know who actually run as a non-admin? I don't; I know I should, but it's a pain in the ass, and I consider myself knowledgeable enough to know how to prevent most issues and to fix any that should happen to come up as a result of vulnerabilities.