MS Issues Emergency IE Security Update
WrongSizeGlass writes "CNET is reporting that Microsoft has issued an emergency patch for 10 IE security holes. 'The cumulative update, which Microsoft announced on Monday, resolves nine privately reported flaws and one that was publicly disclosed. ... Software affected by the cumulative update addressing all the IE vulnerabilities includes Windows 2000, Windows XP, Windows Server 2003 and Server 2008, Vista, and Windows 7.'"
Amazing... that was only a week ago!
If it ain't broke, DON'T fix it.
Ms link here:
http://www.microsoft.com/technet/security/Bulletin/MS10-018.mspx
No real sweat for IE8 on Win7...
Link 1
Link 2
If this is an IE bug, why does it only affect some operating systems and not others?
If this is really an issue with the OS support used by IE, then wouldn't it affect Firefox etc?
Patch releases really need a "info for geeks" section.....
This is normal. Expected. Everyday life for millions of Windows users.
Deleted
Following that link, I see:
That's pretty old. I'm using Opera 10.10 (on FreeBSD) here...
Caveat Utilitor
I just don't use any browser. I refuse to use one that is not 110% secure. Plus it saves me tons of money by not having to pay for internet connection. When I really need to cruise the web, I just plug in the brainstem actualizer and use an avatar to swim through a virtual reality version of the net. And I fight off viruses and malware using a lightsaber. Ya'll really need to come to the real geek heaven.
If only /. were populated by people using a minority operating system that had comprehensive package managers to take care of their updates.
it may be fast, but it sure SUCKS!
Wealth is the gift that keeps on giving.
Grrrrr!!!
And yes, that was a rhetorical question.
We all know that one major problem with the Microsoft platform is that it's homogeneous. No matter how many times we hear the "ground up" reengineering story, we get these exploits that work vulnerabilities in a common code base. All of the platforms use the same code. All code has bugs, and one bug might grant entry, while two more might grant privilege escalation, and so once an exploit is found all the machines with that code base are pwned. The solution to this problem is deviously simple: do everything differently on every machine. No, I'm not talking about ASLR here, though that's a start.
Stop. I know the first reaction to that is "that's crazy talk". This is pretty revolutionary thinking. It's not possible to design a unique operating system for every user. It is however possible to avoid the complementary vulnerability trampoline by varying the ways that components implement various technologies.
Every action that a machine can perform can be done in various ways - various algorithms can be used to achieve the same result, and some algorithms are more efficient than others. As a part of development many of these ways are explored and until now all but one was discarded. Simply by retaining the discarded algorithms, exploring the variations permissible within the defined interface, and retaining each functional implementation as a heuristic option allows the system designer to thwart the advantage of the large static target. The varying algorithms can be distributed randomly across the installed base as polymorphic patches. As long as the variant algorithms are strictly conformant to the well-defined interfaces, and the interfaces are well designed, it works. The downside to this is that some algorithms are, let's face it - sub-optimal. The diversity of algorithms is an advantage here as a feedback mechanism will reveal optimizations that yield net losses due to secondary effects. This will winnow the dozens of algorithms to a few. Even with only a few performant options per algorithm given the vast number of subsystems in a desktop or server operating system, we'll not run out of permutations before the end of time.
When each subsystem might be any one of several implementations that achieve the same object, the monolithic cathedral of code with a universal backdoor is prevented. Patches can randomly rotate the heuristic until the exploitability of individual platforms is not predictable. Performance of an individual system will vary to a degree, but not necessarily so in net - the distribution of performant vs sub-optimal algorithms can be intelligently distributed so that they average out and one system doesn't have all sub-standard algorithms. Positive feedbacks can indicate exploited components and replace them in an evolutionary fashion before they can be combined synergistically into a chain of exploits that go from basic entry to system privilege. The feedback can also gauge the quality status of the code, and with proper tracking lead back to the outstanding developer for recognition (or the leakmaster for reassignment).
Oh, and no patenting this stuff you bastards! This comment is prior art (ok, I adapted the ideas from some 1980's AI research and Conway's Life - but you can't prove that. Regardless, you didn't invent this stuff and the patents are NOT YOURS).
Help stamp out iliturcy.