Why prompt for my own password?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Why do I get prompted to enter my own acount's password? I'm logged in as a
user (not administrator) and in some cases I get prompted for admin password;
this is fine. But in other cases I get prompted for Admin password or my own
account's password. If I type in my account's password, I am alllowed to
complete the change. If my account has rights to make the change, then
shouldn't I only be prompted to confirm the change? Does this sound right to
anyone else, or is this just me?
 
Hello,

I agree - I think you should only be prompted with Continue/Cancel if your
account has rights to do the operation. I also think this should be
configurable via group policy - it is not.
 
If you are logged in as a user with Administrative rights you should not be
prompted to enter your password every time you want to access a
"Administrative" program, or delete a shortcut off the desktop.. Etc.. There
should be a check box that says something along the lines of "Do not show
this in the future" or "Always use this choice" like entering a secured
location or running an executable.

Jason
 
If you are logged in as a user with Administrative rights you should not
be
prompted to enter your password every time you want to access a
"Administrative" program, or delete a shortcut off the desktop.. Etc..

You are not asked for your password if you are logged in as an
administrator. You are simply asked if you want to continue.
There
should be a check box that says something along the lines of "Do not show
this in the future" or "Always use this choice" like entering a secured
location or running an executable.

Hopefully in the future this will be possible; however, right now allowing
this to happen would effectively make UAC worthless, because this would
allow malware to easily bypass UAC and take over your computer.
 
If you have a "Remember this option" check box for lets say, accessing device
manager. I don't see why this would allow malware to get into your system.
There are certain things that you access on a frequent bases that aren't
going to hurt your system that should not prompt you every time.

:
 
If you have a "Remember this option" check box for lets say, accessing
device
manager. I don't see why this would allow malware to get into your system.

Device manager runs inside of the microsoft management console - in effect,
you would have to "checkbox" the MMC. If you did this, a malware would be
able to start an instance of MMC and using command-line switches or some
other method, cause it to do an operation on your behalf, such as open disk
manager and format your hard drive.

Also, imagine the case where you checkmark the command prompt - a malware
could open a command prompt and then perform any operation it wanted - it
could even use that "admin" command prompt to run other software with
"admin" permission!

The problem here is that the computer doesn't know the difference between
YOU starting a program and a program starting a program. If this could be
ascertained, the system could make better decisions as to when to ask you
for permission.
 
Dear Mr. Jimmy (isn't that a line from a Rolling Stones song?),
Why do you defend UAC so much when it's an inconvenience for the majority
of 'heavy', well informed, home users? It should be simple: turn the
freakin thing off. I just recently installed RC1, and I get prompted for
every *uckin program I run. Surely there's got to be a better way (and don't
call me Shirley).
 
Why do you defend UAC so much when it's an inconvenience for the
majority
of 'heavy', well informed, home users?

I am trying to explain UAC to people who think it is JUST an inconvenience
for the majority of heavy, well informed home users. Because that is not the
case. Sure, it may be an inconvience, but it is also an inconvience when a
program with admin powers runs that you don't know about.
I get prompted for
every *uckin program I run.

If you run administrative tools you will get prompted. Don't you want to
know when a program uses admin powers? If you don't, it's easy, turn it off.
But I imagine the majority of "well-informed" home users will enjoy being
able to control which programs run with admin powers.
Surely there's got to be a better way (and don't
call me Shirley).

Perhaps you can share some of your ideas?
 
Back
Top