Not at all Valdis. Keep UAC exceptions for Desktop Settings, Keyboard Settings, Mundane / Trivial. Prompt from UAC on regedit32, reg, secedit, gpedit, the proggy that modifies uac settings. Most "Joe Sixpacks" will never touch any of that, and power users that do will understand why they're being prompted.
Wow that -was- a bitch. This reminds me of when sp2 came out and you could just pop registry keys in allowing your naughty program to execute before it attempted to access the net. On Mon, Feb 2, 2009 at 2:07 PM, <[email protected]> wrote: > On Mon, 02 Feb 2009 20:47:41 +0200, James Matthews said: > > > > http://www.istartedsomething.com/20090130/uac-security-flaw-windows-7-beta-proof/ > > > > Windows is like swiss cheese! > > The biggest issue here is that although it's technically easy to fix this > problem (just have UAC issue an alert when somebody's messing with the > system settings), it involves doing more of what end users dislike most > about UAC (it issuing alerts to Joe Sixpack all the time when he does > something bone-headed security-wise). > > Fixing this one in a way that users will put up with will be a bitch. > > _______________________________________________ > Full-Disclosure - We believe in it. > Charter: http://lists.grok.org.uk/full-disclosure-charter.html > Hosted and sponsored by Secunia - http://secunia.com/ >
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
