New Windows exploit: "Shatter"

[Tobiasly]

You're misinterpreting my reply, Maggie. Headsplice asked "why not plug holes along the way", as if this were simply a buffer overflow or other such common "hole" in Microsoft's software. When I say "this isn't a hole", I mean this isn't something they can just apply a simple patch for.

So yes, it's a friggin' big <I>security</I> hole, but it's not a hole in the sense of a bug, or an inadvertent side effect of a particular operation that a program performs. It's the very underpinnings of the way processes communicate with the OS. They designed the OS to operate this way. It just turns out it's not a very good design.

And my "Which of those solutions would you suggest?" was rhetorical. Again, pointing out that the notion of Microsoft "fixing" this problem in a simple service pack isn't gonna happen.