Full Disk Access in macOS 27.3
Apple (Hacker News, MacRumors, 9To5Mac, MacStories):
In macOS 27.3 beta 2 today, we’re introducing increased transparency and more granular options for two of the APIs: Device Control and Data Access, and Full Disk Access. Before granting an app such extraordinary access, users should understand that it puts all of the data on their Mac at risk. These changes are designed to help them do that and to empower them to make informed decisions about their own data and privacy.
[…]
Developers should be prepared to adjust how they onboard users and make sure their apps can gracefully handle having access to only a limited set of folders or apps when utilizing these APIs. Users will see these updates when approving new app permission requests. All app permissions previously granted by users will remain in effect.
Developers of apps that use Full Disk Access for disk backup, or the new Accessibility settings to provide assistive technologies, can request entitlements to deliver the same experience for new installations that they offered before macOS 27.3.
An app might ask you to give it access to all of the files on your Mac, or to let it control your Mac. When you turn on access for the app in Privacy & Security settings, depending on the app, your Mac prompts you to:
Allow or not allow the app to have access. This option appears for some apps, such as backup apps that ask for Full Disk Access[…]
Choose specific protected folders or apps for the app to access instead. […] It allows the app to access only what you choose, while system protections stay in place for the rest of your data.
System Settings now says: “Full Disk Access is designed only for apps that need to copy or scan all of your data, such as backup and security software.” When you add an app, the default button is Choose Folders. If you instead click Bypass System Protections, it asks you to separately click a red OK button for each type of data that could be accessed, and only then does the Turn On Full Disk Access button become enabled. Then you have to enter your password and click Modify Settings. If an app has Full Disk Access, the Files & Folders settings will permanently show a ! and a red stop sign next to it.
Crucially, there remains no API for any of this. Apps cannot tell the system which folders they need access to, nor detect which folders access has been granted for. They have to present a user interface or documentation that instructs the user to go to System Settings, select the folders (so this is even more steps than before), and click all the confirmation buttons. Apple says:
If you’re not sure which protected folders or apps to choose, contact the app developer.
Since macOS 10.15, apps that tried to access protected folders have (usually) been pre-populated into the Full Disk Access list, so all you had to do was click the switch button to enable access. This no longer seems to happen—you have to click the + button and locate the app on disk. Many apps instructed the user to drag and drop the app icon (since that’s easier than using an open panel, especially if the app implements a floating proxy icon that you can drag), but in macOS 27.3 Apple has removed drag and drop.
I still think a purpose string is likely in the future, but it may be redundant if Apple expects developers to provide their reasons in their onboarding and documentation.
The other missing piece, from my point of view, is that there should be an option for read-only access. As a user, I’m more comfortable granting access to share data if I know that an app can’t mess it up. (I block most apps from network access with Little Snitch to prevent exfiltration, so I’m less worried about read access.) As a developer, I don’t want to ask for more access—and possibly scare the user—than I actually need.
My test Mac has multiple copies of my app installed. They show up separately in Files & Folders, but there’s no way to tell which is which. Each time I click on something in the list, the order changes. Removing one removes the others, too.
Design aside, there’s the question of how well this actually works. I continue to receive support requests from customers (including just this morning) where TCC isn’t working properly. Apps prompt for Automation access but don’t show up in the list. Or the user adds an app for Full Disk Access but it doesn’t show up in the list. Sometimes you can get Full Disk Access working again using this (undocumented) Terminal command:
tccutil reset SystemPolicyAllFiles
There are also undocumented TCC services like SystemPolicyDocumentsFolder for the Documents folder. I’m not sure what you’re supposed to enter to reset user-specified Files & Folders. The man page hasn’t been updated since 2012! I guess you could try:
tccutil reset All [bundle-id]
but that’s annoying because then the user has to re-apply all the other permissions.
Unfortunately, these Terminal commands to reset the database often don’t work. Then the user has to boot into Recovery mode and turn off SIP in order to fix the problem (and then re-enter all permissions for all apps). Sometimes even that doesn’t work, and macOS needs to be reinstalled. It’s a mess.
I’m installing it now, but from what I’ve seen so far, these changes not only alleviate my concerns that Apple might over-tighten the screws, I actually think they add clarity and give users more, not less, control over their Macs.
At least at present, the additional controls for “full disk access” aren’t additional controls for FDA at all; they’re controls for other things.
Phew. I don’t think SuperDuper is affected. At least, it’s working here…
It’s not clear to me what the entitlement for backup apps does—just bypass some of the scare screens? Or is some functionality now off-limits unless you have the entitlement (or perhaps disable SIP)?
I think this is a very considered design. The previous settings for these permissions seem slapdash in comparison — like a lot of the “new” Mac System Settings panels.
[The] real story here is that dialog box. Are we seeing a return to sanity in dialog box layouts? The window isn’t skinny, the buttons aren’t stacked, there’s a divider line between the content and the buttons…it actually looks good!
Just from a testing viewpoint this UI drives me nuts.
What are the odds an app is handling all combinations of users allowing or disallowing certain things? What are the odds the user even understands the implications of doing so?
An app should be able to come up with the combinations it requires (ideally one!) and present those in user-understandable ways (not to mention fewer things to actually test, ensuring they work for the user).
The new macOS 27.3 beta 2 introduces not only an extremely scary dialog to assign Full Disk Access to an app, but apparently includes a lot of other changes to “protect” users.
The
[NSFileCoordinator addFilePresenter:]API for example, doesn’t work anymore when opening Core Data files with SHM and WAL subfiles, because “The related item is protected by a different storage class than the primary item.”Not sure if this is a bug, or intended, or a side effect of other security changes.
This arguably makes macOS more agent friendly for the greater public than before
Because the granted permissions can be more granular.
Has Jason Aten ever come clean about having enabled Full Disk Access for Muse?
Because none of these changes in macOS 27.3 address Aten’s wild claim that Muse could access Messages without Full Disk Access.
Previously:
- System & App Protection Override
- Unspecified Full Disk Access Screw Tightening
- Apple Still Sitting on Entitlement Requests