OSNews

Are you serious? I'm not saying it should never ask again about anything, but give me the option to say I trust this executable. It's like saying "you're trying to use an unsigned grep, do you trust it?" and then five minutes later "you're trying to use an unsigned grep, do you trust it?", and again, and again, and again, ad infinitum.

[q]The reason why you can't say "yes, and don't ask me again" is because the next time it comes up, it might be caused by something malicious.[/quote]

Did you read the whole request, he wants it on a per-application basis. What is so hard about UAC running an md5 against the exe file in question, store the result of that exe so that the next time it is loaded it is just a matter of a quick check against the stored md5 to see if it is the same exe - and allow the application to run?

Geeze, I thought of a solution just then that addresses the fundamental problem and the perceived security implications in under a minute. It isn't rocket science - just good old fashioned commonsense.

IT'S NOT POSSIBLE!

First example:
1. user executes destroy.exe: UAC prompt, user clicks on "always consent"
2. malware executes destroy.exe, no prompt because the exe is the same.
-> you're pwned!

Second example:
1. user changes a firewall rule: UAC prompt, user clicks on "always consent"
2. malware changes a firewall rule, no prompt because the firewall configurator executable is the same.
-> you're pwned!

Third example:
1. user copies a file in c:\windows using windows explorer: UAC prompt, user clicks on "always consent"
2. malware copy a trojan in c:\windows, no prompt because the copy command executable or the explorer.exe is the same.
-> you're pwned!

Edited 2008-07-25 08:31 UTC