Wednesday, October 18th 2006
Microsoft releases Windows Internet Explorer 7
The release notes can be found here, and you can download the final version for yourself here. IE7 will only work if you are running Windows XP or Server 2003. Among the main changes is a shinier interface, the addition of tabs, and the ability to place add-ons in. You can see a list of the add-ons here.
Source:
Microsoft
17 Comments on Microsoft releases Windows Internet Explorer 7
personally i'm sticking to FF...
We set him up w/ this release & likes it (tabs & such appealed to him, over IE6 separate screen instances, for instance, & also he says its faster (makes sense on debug code removal alone)).
I told him about it, & while @ his place, we updated him cleanly & easily... + it seems to work well enough...
:)
I wonder if a Windows Server 2003 SP1 release model is out?
(Anyone know??)
APK
P.S.=> I'll install it myself, just for the fact its libs that other apps may depend upon are probably cleaner too...
See, YES: IE6.x for Windows Server 2003 SP1 (& even @ install) is different from other OS by MS, & that it defaults to a more secure initial setup!
(A lockdown/secure mode by default (& Really? Largely, that default secure mode, is what I've personally been doing to EVERY BROWSER for a decade on the public net anyhow - turned off java/javascripts & ActiveX control use))...
Still, I'll install IE7 because it's doubtless used by other apps (like your OS shell desktop for instance as an example, & yes, the explorer.exe file mgt. portion (though, you can turn off LARGE portions of this in Explorer.exe options)), & is probably more secure than ANY past builds NOT ONLY in configuration options, but in its libraries as well!
Superior doubtless to even the IE 6.x version in Windows Server 2003... apk
Answered my own question from above, lol, w/ THIS answer from MS' servers for IE 7 for Windows Server 2003 SP1:
You tried to access the address switch.atdmt.com/action/IE_7_Windows_Server_2003_SP1_B, which is currently unavailable.
Please make sure that the Web address (URL) is correctly spelled and punctuated, then try reloading the page.
Make sure your Internet connection is active and check whether other applications that rely on the same connection are working.
Check that the setup of any Internet security software is correct and does not interfere with ordinary Web browsing.
If you are behind a firewall on a Local Area Network and think this may be causing problems, talk to your systems administrator.
Try pressing the F12 key on your keyboard and disabling proxy servers, unless you know that you are required to use a proxy to connect to the Internet. Reload the page.
:(
* Oh well, I can wait...
APK
Because of the DLL/libs that IE 7 has, that the Operating System itself, & other apps utilize!
IE (in any form from 4.0 onwards iirc, & certainly 5.0 onwards) is MOSTLY an "HTML rendering engine"!
That engine/libs/dll's set of files are ones that apps like Office use like mad!
(All so they do not have to rewrite the functions into the .exe's for Office itself... the apps just call functions that are proven & prebuilt from said libraries to render HTML based content & so the "document-centric" vision of computing from Microsoft can come true, in a consistent manner (it's NOT application centric on documents anymore, any apps can use other apps data, etc. type of thinking, w/ proven + prebuilt code routines for it))
That said?
Since IE7 is more secure (even moreso than IE 6.x in Windows Server 2003 & for the reason I note on the previous page in my first post)?
That means ALL of MS' apps that depend on it (like Office &/or the OS desktop Explorer shell too no less), & will gain via IE7's cleaner security on ALL of their OS' that can use IE7...
APK
...............
oh wait......its already there, how convenient :D
See my subject-line/title of my reply here, above, & this URL:
secunia.com/Internet_Explorer_Arbitrary_Content_Disclosure_Vulnerability_Test/
:(
* It's one they left in that has existed since IE6.x no less... but, turn off the javascript? No bug...
Personally? I think I actually "lucked out" because I eventually was able to D/L IE7 for Windows Server 2003 SP1, & it will NOT install here!
(No matter what: Plus, & I traced its install using regmon by SysInternals & FileMon as well to see what/where parts of the system it is writing to when it installs)...
In the end, I figured it was registry path/key/value rights (because I limit this using ACL's like most folks may in filesystems on disk), so I "relaxed" them on HKLM/HKCU - Software/Microsoft/Internet Explorer but, no dice!
APK
P.S.=> Anyhoiw/anyways, on this "newly discovered bug":
This is WHY I turned off Java/JavaScript/ActiveX usage years ago (circa 1997 onwards), & have been recommending that for folks using IE especially on the "public internet" @ least (as Windows Server 2003 has done in its "security-enhanced" build of IE6.x, no less) in system tuneup type documents I've auithored & placed online for others to use from that same time-period (1997 onwards to present)...
It works to stop these things that are script-based & extensions based holes, period!
I recommend others do so as well until they KNOW FOR SURE that the sites they go to that demand the use of ActiveX/Java/JavaScript are "clean" & 110% trustworthy... apk