Halcyon - "It's obvious who are the zealots, this problem only happens in XP, not even in any of the other Windows versions, not in Linux, not in OS X"
Oh good grief, I feel like I'm talking to a child. Why can't you listen to the discussion and learn from it? Why must you keep repeating the same points over and over again even though they've been shot down?
The reason why this is only a problem in XP is because only XP supports this shell: mechanism. Linux, OS/X and such do not. But the problem exists in Mozilla because it implicitly trusts everything sent to it by a web server, even if it doesn't know what that is.
So the behavior was to pass this of to the OS to process. Which I can understand why they might have done because the OS would handle a rm: descriptor for Real Audio, or a mms: for Windows Media, or any number of other examples. But the problem is that while a shell: call is a perfectly reasonable operation when performed locally on the Windows box, it's not something that should be passed off by a browser to the OS when executed from a remote location.
"yet the improperly patched flaws in IE just don't seem to matter! "
Nobody ever said that. I think it's a very real concern.
However, what I stated last week was that the advice being promoted by a lot of zealots that you should abandon IE and move to Mozilla was ignorant as Mozilla also had security problems and you were promoting a false sense of security to the uninformed end-user.
This week, in a stroke of interesting timing, a major hole was found in Mozilla proving my point.
That's the sum total of my point, that's all I ever stated. I just questioned the Zealots who like to promote fiction as fact. you realize that just because you wish the sky was purple doesn't make it so, I hope?
|