I don't often run into problems, although if I forget and let some application self-update while running as an unpriv'd user, and then go to install an update as Admin user, I have to remember to delete the App and then install the new version due to perms problems.

I suppose that would probably stump my mom.

Haven't checked this behavior in Leopard, yet.

-jml

>>> Roland Dobbins <rdobbins (at) cisco (dot) com [email concealed]> 2007-11-01 14:11 >>>

On Nov 2, 2007, at 1:45 AM, Dave Schroeder wrote:

> But it's a Trojan, which requires user interaction, downloading
> something manually, and expressly granting it administrative
> privileges to your machine.

This brings up an interesting point - how many Mac users go to the
trouble of setting up a nonprivileged account and then do their
normal work under that? I don't know, but my guess is that it's a
pretty low percentage, especially as, at least with Tiger, one runs
into some issues such as borked /Applications perms/ownership which
require a *NIX background to even understand, much less remedy.

How many Mac users have been faced with a seemingly-random request to
grant a non-obvious background app/utility Keychain access, not to
mention commonly-used apps asking for it without an easily-discerned
reason? And in such situation, what do they typically tend to do
(I've my own opinion about this, but clue welcomed).

-----------------------------------------------------------------------
Roland Dobbins <rdobbins (at) cisco (dot) com [email concealed]> // 408.527.6376 voice

I don't sound like nobody.

-- Elvis Presley

[ reply ]