Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

.NET

Review: Mac OS X Shines In Comparison With Windows Vista


True Authentication?

OS X vs. Vista


•  Image Gallery

If I'm going to talk about changes in Vista, then I have to talk about the public face of the new security features: User Account Control. This is something that Microsoft has been talking about nonstop for months, and to listen to them, UAC puts Vista on the same level as Mac OS X and various Linux distributions when it comes to making it harder to accidentally do bad things to your system. The problem is, UAC seems to have confused "authentication" with "approval."

With Mac OS X, if I need to make a change to a system setting or install software in a location that I don't have read/write access to, I have to authenticate to perform that action. For example, I want to change my IP address for my wireless connection, and my system is set up to require authentication to do such things. With the details expanded, I have a fair bit of information. First, I have to know the password of an administrator user for that machine. If I don't, then even physical access isn't enough; I can't unlock that preference pane. Second, I know the right it wants me to authorize: system.preferences (although I may not know what that means, it's there at least), and I know which application is requesting that right.


In OS X, users need to authenticate to change system settings.
OS X
In OS X, users need to authenticate to change system settings.

(click image for larger view)

view image gallery

If I attempt to perform the equivalent action in Vista, I don't actually have to "authenticate" anything. There's no need for a password. Anyone sitting at this computer can take this action. What you see for UAC as an administrator is basically a dialog that says, "You want to do this?" I don't get any information about what I'm asked to approve -- all I get is a really long GUID-type number that's of no use whatsoever.


Vista
In Vista, users need to "approve," rather than "authenticate," changes.

(click image for larger view)

view image gallery

In Vista, users need to ''approve,'' rather than ''authenticate,'' changes.

The other thing is, until I deal with this dialog or it goes away on its own, I cannot do anything else in Vista. The Mac OS X version won't let me interact with System Preferences until I handle the authentication request, but I can at least keep working in other programs.

That illustrates the three worst aspects of UAC and why I think it's going to be called "User Annoyance Control." You get what is essentially an "OK/Cancel" dialog that most users will hit "OK" for without thinking, you may or may not get useful information as to what is going on, and you get locked out of your system until you deal with this. I have a problem with seeing how annoying people is enhancing security. When I say "annoyance" I really mean "infuriate," because you get UAC dialogs all over the place, and you're never sure when or why you're going to get them.

For example, when I installed Adobe Reader 8 in Vista, I had to deal with UAC twice. The first UAC dialog box was in response to launching the setup file, something I had done with a manual double-click. I could understand authentication if it had been launched by another unauthenticated process, but a manual double-click? Now, since we're running an installer, there is some justification in authentication, but for one thing, that's not what we're doing here, we're just approving, and for another, what if I want to install this into my home directory? What if I want to install this into a place I have full access to? Requiring UAC approval for every install either means the installation process is rather inflexible, or that every installation changes system-level data regardless of need. Neither idea is terribly comforting. However, the second dialog box let me finish the installation.


Vista
Vista Installer user-account-control approval dialog.

(click image for larger view)

Vista
Second Vista user-account-control installation approval dialog.

(click image for larger view)



Vista Installer user-account-control approval dialog.


Second Vista user-account-control installation approval dialog.




view image gallery


I've seen worse. If you use Vista under Parallels on Mac OS X, the Parallels tools installs something like eight drivers. You have to UAC every ... single ... one. But even when I've taken actions where Vista is telling me "You will have to authenticate," I still only have to click the correct button in a dialog. That's not authenticating anything, it's just approving. There's no way that UAC is going to enhance security, in fact, it's probably going to have the opposite effect, because people are going to just hit OK/Continue even more automatically than they do now. If, as everyone knows, Apple and Microsoft borrow/steal from each other liberally, I really wish Microsoft would have done a better job with regard to UAC. Adding "Annoyance +20" to the OS is not the right answer here.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.