Microsoft's Anti-Spyware program is causing troubles for people who also use Symantec's Norton Anti-Virus software; apparently, a recent update to Microsoft's anti-spyware application flags Norton as a password-stealing program and prompts users to remove it
even if you're renting you've got more rights than if you're using windows.
Now most windows users need anti-spyware stuff too, again as a band aid for the Windows crappy security. It's inexcusable, and pathetic, for one security band-aid to disable another.
This paper presents a new generation of attacks against Microsoft Windows, and possibly other message-based windowing systems. The flaws presented in this paper are, at the time of writing, unfixable. The only reliable solution to these attacks requires functionality that is not present in Windows, as well as efforts on the part of every single Windows software vendor. Microsoft has known about these flaws for some time; when I alerted them to this attack, their response was that they do not class it as a flaw - the email can be found here. This research was sparked by comments made by Microsoft VP Jim Allchin who stated, under oath, that there were flaws in Windows so great that they would threaten national security if the Windows source code were to be disclosed. He mentioned Message Queueing, and immediately regretted it. However, given the quantity of research currently taking place around the world after Mr Allchin's comments, it is about time the white hat community saw what is actually possible.This paper is a step-by-step walkthrough of how to exploit one example of this class of flaw. Several other attack methods are discussed, although examples are not given. There are many ways to exploit these flaws, and many variations on each of the stages presented. This is just one example.
http://security.tombom.co.uk/shatter.htmlDoes anyone know if MS has fixed that exploit since?
Yea, it cannot be fixed as long as win32 api is being used. However, as more and more applications move onto .NET, the whole win32 subsystem might become obsolete in the future. With that, its design flaws will also vanish into oblivion.
I don't know anyone anymore who still runs win98 for any real purpose. Well, I think my sister might still use it on one system since she has hardware that doesn't have drivers for anything else. Or perhaps even she doesn't, not sure. The point is, win98 is basically gone already.