|
|
|
| Authored by: mcinsand on Tuesday, July 17 2012 @ 10:06 PM EDT |
I have no doubt that it's possible, but I also have no doubt
that decoupling IE from Win is not as trivial as it was for
Win95. My preference, of course, is to decouple the PC from
Windows :D[ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Wednesday, July 18 2012 @ 12:01 PM EDT |
The lingering IE code would still respond happily to file://-protocol requests,
and will be run automatically for any content type that's hard-associated with
IE, like .mmc plugins or HTML help. The malware payloads can easily be delivered
by other apps that DO have network connectivity (e.g. saved email attachments or
downloads from another browser), or via an infected removable drive, and
probably in other ways that I can't think of off the top of my head.
IE doesn't need a network connection to pwn you. It only needs to exist, and
for the OS to be programmed to ALWAYS run it (no exceptions) in certain
circumstances. MS essentially guarantees those two criteria to be true.[ Reply to This | Parent | # ]
|
| |
| Authored by: jonathon on Wednesday, July 18 2012 @ 01:45 PM EDT |
>the removal of the specific portion which performs http/https connections
would result in the effective functional removal of the browser.
I removed MIE from Win2K. Whilst I didn't have any issues with the software I
normally used, I did run into problems installing software that required a
browser, and would, in theory, be able to use any browser. Renaming Firefox
"MIE" did solve some of those problems, but not all of them.
There is a lot more software in the Windows world that requires MIE to be
present, with http/https connectivity setup, than one would expect.[ Reply to This | Parent | # ]
|
|
|
|
|
