|
UAC not a "security boundary."
Does anyone know, why MS does not consider UAC to be a security boundary?
And what are the trade-offs involved with making it one? Is it not possible
to make it a security boundary? It seems kinda anti-customer to say "if we
find a security exploit in our code (in UAC) we won't fix it," doesn't it?
I wish this would be fixed in Windows 7, but I admit I don't understand all
the issues involved, so any help would be nice.
|