Comments on: Why doesn't my computer trust me anymore?

Question: Why doesn't my computer trust me anymore?

Brandon Blatcher — Thu, 12 Oct 2006 17:04:03 -0800

Even though I'm the admin, my Mac OS 10.3.9 suddenly wants me to authenticate common actions. What the hell happened?

This evening when I turned on my Macintosh and began working, it begin asking for authentication every time I tried to move a new app to the Applications folder or tried to delete a file. Everything else seems to work fine, like it did before.

Anyone know a reason for this strange new behavior?

Mac OS X 10.3.9, G4 Mac, yeah, i'm the admin and sole user account.

By: jjg

jjg — Thu, 12 Oct 2006 17:10:35 -0800

Sounds like a job for "repair permissions". I know, I know, it's often used as a voodoo incantation to fix anything that goes wrong, but this sounds like the sort of case where it would really apply.

By: filmgeek

filmgeek — Thu, 12 Oct 2006 17:17:51 -0800

Actually, it sounds like something borked a major permission.

This might be fixed via Disk utlities's "Repair Permissions..."

But it could just as easily be something at the system or library level whose permission isn't yours (it probably used to be yours) and now requires authentication every time you make a change/launch an application.

Defintely run Disk Util., repair permissions and check back.

By: runningdogofcapitalism

runningdogofcapitalism — Thu, 12 Oct 2006 18:09:28 -0800

Failing that, try creating a new user account giving it admin permissions. Log into that account and see if you can replicate the problem. If not, then you know something's borky in your user setup.

By: Brandon Blatcher

Brandon Blatcher — Thu, 12 Oct 2006 18:17:04 -0800

Well, I ran repair permissions and attempted to repeat the problem via deleting files or moving a new app into the Application folder. No authentication problems.

How do permissions get messed up anyway?

By: Brandon Blatcher

Brandon Blatcher — Thu, 12 Oct 2006 18:19:02 -0800

but this sounds like the sort of case where it would really apply.

Really, why's that? I'm curious...

By: migurski

migurski — Thu, 12 Oct 2006 18:25:25 -0800

Really, why's that? I'm curious...

Mac OS X asks for an administrator's password when you try to do something for which you don't have permission. If every minor action triggers the alert, it's likely that permission settings on some crucial file or folder were changed to disallow normal access by the owner. "Repair Permissions" changes the permission settings for certain files (system stuff, library stuff) to what it believes is right & normal for typical use, so it makes sense for this case.

By: pmbuko

pmbuko — Thu, 12 Oct 2006 18:34:07 -0800

Permissions don't "mess up" on their own. Outside a user directly changing the permissions, the most common cause is a badly written software installer. The second most common cause is drive or directory corruption.

Best practice for Mac OS X is to have all your applications owned by the root user and the admin group, with rwxrwxr-x (775) permissions.

By: adamrice

adamrice — Fri, 13 Oct 2006 08:15:31 -0800

FWIW, you can inspect and edit this stuff using the humble "get info" window. I'd get info on the Applications directory and see what it saysdisclose the "details". On my machine (at least) it is "owner: system (read write) /group: admin (read write) / others (read only)"

I agree that this sounds like one instance where running "repair permissions" might help.