Microsoft Improving User Account Control

The "double prompts" are probably most annoying. For example, if you want to copy a file or folder to c:\program files, you get two prompts. One saying that you need administrative privileges and then the actual UAC prompt.

It's a good feature and an important part of a secure system, but the implementation in Vista is a bit lacking. At least developers of 3rd party programs have learnt to not trigger UAC prompts for everything, so it's far less annoying now than it was when Vista launched (and Apple kept making fun of the feature even though Linux and OSX have had similar featues for ages).
 
That all depends on implementation.
No, it doesn't. In your example it would allow the Malware right on through.
That's the problem with doing per-session stuff is it still opens the door for malware.

Right, it's not exactly the same, but similar in theory. Sudo requires use of a password when first initiated and enables a temporary admin level privilege. I'd like to see something similar in for UAC.
All in a command prompt.
Generally, folks in a command line know what the heck they're doing. Regular Windows users do not.
 
No, it doesn't. In your example it would allow the Malware right on through.

Do a check to see where the command was issued from, if it wasn't from the same source that was granted install rights, then don't allow and prompt user. That's just one possible implementation.

All in a command prompt.

There are other ways to set a temporary admin level account, it doesn't have to be within a command line.
 
Do a check to see where the command was issued from, if it wasn't from the same source that was granted install rights, then don't allow and prompt user. That's just one possible implementation.
You mean like it issued by COMPUTER\bonsai... guess what? Malware will just run it as COMPUTER\bonsai as well!

It's flawed.


There are other ways to set a temporary admin level account, it doesn't have to be within a command line.

Propose one...
 
I don't get the people saying UAC isn't sudo. The two are actually pretty similar implementations of the same idea, sudo just does it better. And no, you're not required to use sudo on a command line - look at Ubuntu for an example of sudo done within the GUI. I believe the package responsible for this is "gksudo."

And you can already make UAC prompt for a password if you want it to (and I do). Just change your account type from "Administrator" to "Standard User" in the User Accounts control panel. I'm apparently in the minority in thinking that UAC isn't that annoying, so if you already dislike UAC, you'll probably hate this.

Then again, maybe it's the software that you're using: developers have known since Windows 2000 that you're not supposed to be writing to Program Files anymore, yet many still do, which causes a UAC prompt.
 
UAC really annoyed me at first, but then I did some research and figured out how to do it the way I want it. It required some slight registry tweaking (Vista Home Premium), but now my admin account has UAC disabled, and my user account has UAC enabled so that if I want to perform an admin action while running as user (Say, installing a game or running Folding@Home), I still have the option to run as admin. Any serious admin system-level work I need to do (Drivers and etc.) gets done on Admin, where UAC won't bug me and I'm not doing anything that'll give Malware the chance to take advantage of its access.

UAC works well when you set it up correctly. The problem is that setting it up correctly is something of an adventure. The real issue is that UAC is targetted toward Joe Average who needs to be protected from his own stupidity, but only a power user understands its benefit and doesn't click 'continue' when he doesn't need to. Those same power users get annoyed by all the security popups.
 
Annoying the hell out of people who dont need to be hand-held and annoying the hell out of people who dont understand what the prompts mean anyways is progress?

Sure smart ass. That is why I agreed with the previous poster about the implementation was incorrect. Advanced users like use do not need to have our hand held...that really frosted a lot of people.
 
Propose one...

with sudo (more specifically gksudo so you get a nice GUI popup so no command prompt) it provides permission escalation (it is triggered by a root application). The user has this elevated permission for a set time and if they are no longer running a root app the timer starts, if they re-start a root app the timer restarts

it is really easy todo and has been done for years
 
Advanced users like use do not need to have our hand held...that really frosted a lot of people.
UAC isn't "hand-holding", and any "Advanced" user that thinks so is vastly mistaken.


The user has this elevated permission for a set time and if they are no longer running a root app the timer starts, if they re-start a root app the timer restarts

I guess they could do that.
However, you can't disagree that it does not decrease the security of the system.
Malware could just wait around for that timer.
 
I guess they could do that.
However, you can't disagree that it does not decrease the security of the system.
Malware could just wait around for that timer.

Never said it wouldn't (and watch the double negatives)
sudo and UAC are just conveient means to gain root/admin access for system level control (its just one is a bit over-zealous and its intention has now been lost in the end-user).

YES if someone entered gksudo and gained temp root-access ANYTHING during that period that is SUID for root would be run, that doesn't mean already running apps automatically get boosted access OR app that don't need root access get run as root. IE malware wouldn't be as big as a problem as you are thinking

All MS needs todo is mimic UNIX permissions and explicilty state some apps are admin-level and then UAC starts gaining some relevance
 
that doesn't mean already running apps automatically get boosted access OR app that don't need root access get run as root. IE malware wouldn't be as big as a problem as you are thinking
Sure it would.
Malware run on a user-level can still ask for a root-level item.

Again: decreases security.

BUT a stupid user can compomise any security you put inplace
Yea, but at least UAC is still attempting to stop it...
 
Back
Top