W
Will Niccolls
"Jimmy Brush" .
Well, ok, but the problem with this is that 95% of humans that use computers
don't have the requisite knowledge to understand what "trusting" a program
means. They barely know what "delete" means, they don't know what a
shortcut is, they don't understand what a user account is, and they sure as
hell don't know how to judge whether "iexplore.exe" vs. "ajksdka2.exe" is
trustworthy. The prompts that MS is so fond of simply become clickable
hurdles to jump past as fast as possible.
Programmers and most system admins have little understanding of what most
end user's knowledge is so they just can't offer language that makes sense
to them. Programmers use language like "Information you exchange with this
site cannot be viewed or changed by others, however, there is a problem with
the site security certificate".
Non-programmers have no clue what the hell that sentence means. They don't
know what a site is, they don't know what a security certificate is. They
click yes and keep going. Prompting users isn't effective security in my
view--(which is ten years as a help desk/tech support/sysadmin). It's
annoying and largely useless.
So, to recap, UAC:
* Ensures that you TRUST a program to have complete control over your
computer. This prevents programs that you do not trust from gaining
complete access to your computer against your will. (EX: "I don't know
what ajksdka2.exe is, so I will not allow it to run with complete control
over my computer.")
Well, ok, but the problem with this is that 95% of humans that use computers
don't have the requisite knowledge to understand what "trusting" a program
means. They barely know what "delete" means, they don't know what a
shortcut is, they don't understand what a user account is, and they sure as
hell don't know how to judge whether "iexplore.exe" vs. "ajksdka2.exe" is
trustworthy. The prompts that MS is so fond of simply become clickable
hurdles to jump past as fast as possible.
Programmers and most system admins have little understanding of what most
end user's knowledge is so they just can't offer language that makes sense
to them. Programmers use language like "Information you exchange with this
site cannot be viewed or changed by others, however, there is a problem with
the site security certificate".
Non-programmers have no clue what the hell that sentence means. They don't
know what a site is, they don't know what a security certificate is. They
click yes and keep going. Prompting users isn't effective security in my
view--(which is ten years as a help desk/tech support/sysadmin). It's
annoying and largely useless.