Linked by Thom Holwerda on Fri 15th May 2009 07:11 UTC, submitted by Georgi Petrov
Permalink for comment 363785
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/20/13 6:17 UTC, submitted by MOS6510
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
More News »
Sponsored Links



Member since:
2008-07-15
Please tell me this is some kind of late April Fools joke. Please tell me Microsoft didn't screw up security again...
I don't know why I'm surprised. MS has never been one for eating their own dogfood. It's the classic "do as I say, not as I do" philosophy for them. Their products don't have to conform to the standards they set out for everyone else... well, why not? They're hypocritical everywhere else, why not in their software too?
Leaving aside the complete stupidity of this flaw in the first place... why, exactly, would calc.exe need to be elevated? I just can't think of anything that would require elevated privileges in a *calculator*. Notepad I can understand needing elevation sometimes if you're editing a system file...
I guess it's typical MS: great kernel, braindead userland. Move along folks, there's nothing to see here... yet. I can't wait to see what's going to happen if they don't fix this by release time, it will certainly be one hell of a show to watch.
These stupid (deliberate?) flaws are the reason I will never use Windows as my primary os again, no matter how well it runs or how good it looks.