Live data from Hacker News

You can't trust macOS Privacy and Security settings

eclecticlight.co

131–140 of 175 posts

Re: You can't trust macOS Privacy and Security settings

#131

Earlier quoted context omitted.

Don’t applications running under your user account have access to your user’s home folder by default?

No. You get prompted something like “Application wants access to your Documents folder” and “Application wants access to your Downloads folder” on first attempt of each folder.

The article seems to be saying that is true unless you implicitly and somewhat invisibly grant access via the file picker.

Re: You can't trust macOS Privacy and Security settings

#133
post #36

That's the beauty of using a GUI-first operating system! > only way you can protect your Documents folder from access by Insent is to run the following command in Terminal: tccutil reset All co.eclecticlight.Insent then restart your Mac

Speaking of GUI weirdness, I've seen a couple of relatively newer macbooks do this thing where the laptop is shutdown with wifi disabled, but after login on startup the wifi icon displays the wifi scanning mode as if the wifi is enabled and looking for networks before reverting to the wifi disabled display icon. Is this a GUI bug or is the wifi disabled setting overrided for a split second on startup? I haven't looke…

based on my experience, I suspect the latter

similar, user-hostile behaviors I have found include:

- wifi network passwords are persisted through a system wipe and reinstall in recovery mode - a phone home is required by an activation step during installation - bluetooth is always re-enabled after an upgrade

Re: You can't trust macOS Privacy and Security settings

#134
post #7

The problem with Mac’s sandbox system is that it’s giving me some PTSD of Windows UAC. It’s inventing a solution to a problem that might exist in small doses, but instead gives users permission fatigue. I personally think the traditional *nix model has served us quite well, and elective sandboxing using containers (à la Docker and so on) is quite good. The Mac sandbox model is probably ok for most normal users, but f…

I don't understand why OSX needs to restart the app to grant it permissions. The most annoying is video chat apps such as Teams and Zoom, having to close everything and reconnect if you want to share the screen or such. Perhaps there's a technical reason but it just feels like a lazy implementation.

But about the unix permissions model, is it really useful? During all my years of using linux on my personal machine, I've always had everything owned by my own user. Setting up specific users for programs would be a pain, and I don't think anybody does that? Servers is a different question, because then you're not actively using the system in the same way, which makes managing user accounts and their permissions on an app-level doable.

For normal users I think what's done on iphones and such works fairly well, and there they actually seem to have implemented it properly so that it doesn't require a restart to grant permissions.

Re: You can't trust macOS Privacy and Security settings

#136
post #97
post #81

Earlier quoted context omitted.

No, this is definitely a bug. The Privacy and Security panel is part of Settings, which is definitely part of the OS. Saying the Open and Save panel somehow has priority suggests that the Privacy and Security panel is not looking at the same parameters as the Open and Save panel, ergo a bug.

It’s not a bug and that is clear if you don’t use the documents folder as your example. When granting specific access it is not the same system as when granting general Documents folder access. The UI just doesn’t reflect this.

> The UI just doesn’t reflect this.

That's the bug. Either that or MacOS has two separate/distinct mechanisms for managing permissions, which would be a huge security flaw.

Re: You can't trust macOS Privacy and Security settings

#137

Earlier quoted context omitted.

It would ask for permission.

Every time you relaunch the app?

It depends on the app whether that would make sense. If it is document centric, then yes. The user should explicitly open every time. If it doesn't make sense for the user to open it every time, it should ask for permanent permission and that should be recorded in system settings where it can be removed.

Re: You can't trust macOS Privacy and Security settings

#138
post #97

Earlier quoted context omitted.

It’s not a bug and that is clear if you don’t use the documents folder as your example. When granting specific access it is not the same system as when granting general Documents folder access. The UI just doesn’t reflect this.

> The UI just doesn’t reflect this. That's the bug. Either that or MacOS has two separate/distinct mechanisms for managing permissions, which would be a huge security flaw.

MacOS has two distinct mechanisms. One gates access to Desktop, Documents, etc. for general access. The other grants access through the Open dialog. The open dialog is always superior because it's consent for a specific location.

Re: You can't trust macOS Privacy and Security settings

#139
post #100
post #95

Earlier quoted context omitted.

Doesn’t seem like a bug to me - it’s just a poor UI. Two different security systems both working properly but only one has a UI to show the protections.

Why would you think it's "working properly"? The app somehow gained a permanent permission that I didn't give and that I can't remove no matter what I do. That's not working properly in any sense.

>I didn't give

This is not true, you do give consent when you pick a folder to open

Re: You can't trust macOS Privacy and Security settings

#140
post #72

Is this a bug, security vulnerability, or just an oversight? It’s not clear to me. As a precaution would it be a good idea to run that reset command for all apps?

This is an oversight in the UI. None of the systems are malfunctioning, it's just that there's no affordance in the UI for the implicit consent flow.
Post reply on HN