50 ms·
Actually IE6 and older tied the IE user interface to the Explorer user interface which shared the same SHDOCVW. IE7 created IEFRAME to separate the Explorer use
by yuhong 13y ago
Actually IE6 and older tied the IE user interface to the Explorer user interface which shared the same SHDOCVW. IE7 created IEFRAME to separate the Explorer user interface from the IE user interface, but it is still in system32, and so are all the other core IE components like MSHTML, WININET, etc...
- ksk 13y agoAre you talking about the UI controls or the browser?iexplore.exe could be deleted at any time. Ofcource because explorer.exe also could handle URLs you could technically still browse via it. (Though I'm pretty sure that by default only URLs in the local/trusted zone were allowed) And then I believe the help component also relied on the rendering engine. Although the hcp:// vulnerabilities were in the protocol handler (helpctr.exe) and the ms-help:// vulnerabilities were also in the protocol handler which allowed the attacker to bypass ASLR/DEP.
- yuhong 13y agoTrue, HTML Help definitely relies on the IE rendering engine. And yea particularly in IE6 I don't think iexplore.exe itself does very much.