If an App Asks for Full Disk Access or System and App Protection Override (support.apple.com)

220 points by jshier 16 hours ago

gbdubs 13 hours ago

This is a very poorly conceived API. If developers' use cases don't fit cleanly into Apple's (narrow) idea about how a hypothetical app should work, developers will continue to feel like they need to request these expansive permissions. A good filesystem permission API could include any of these which would make users WAY safer and enable developers to request far smaller scopes:

- Allow the developer to specify the common location(s) that they need access to. Rather than having to have the user select the folder they want to grant access to, have the developer say "this app uses data in these 5 folders, do you want to grant that access" - so much clearer, and useful in cases where an app has to integrate with other apps through the filesystem. - Readonly access. Allow an app to read your files but prevent writes or deletes. - Time limited access. Allow some kind of access and allow the user to auto-expire it rather than having to remember it exists. - Allow for negative access (i.e. allow labels or tags on directories to mark them as sensitive and prevent access by default - browsers could do this for their cookie stores, `~/.ssh` could ship with it as a default, etc.)

Apple could have used this opportunity to think through the question of "why do developers ask for filesystem access, and how can we allow legitimate usage through well scoped access controls", but instead they built a bad API that will (I would guess) not actually allow developers to be more judicious or achieve any of the user-safety benefits.

Apple needs to learn to talk to (and listen to) developers.

geocar 13 hours ago

> This is a very poorly conceived API.

However users are very happy with it.

> developers will continue to feel like they need to request these expansive permissions

And users will continue to seek alternatives, or risk denying said permission.

I don't use any apps that require this permission, and would never use any app that required this permission without an extremely good explanation of why it was needed.

Until that happens, no.

> Allow the developer to specify the common location(s) that they need access to.

Why not just back up: How does the developer know the location. What's common about it?

I'm so not sure they need access to anything yet.

I use Spotify, Slack, Zoom, and WhatsApp: All of them have asked for it, but they all seem to work fine if I deny them access to full-disk access. So I am confident your issue is a non-issue for me and millions of people like me.

I don't have any apps that need this, so I do not want you to blow past this so quickly with the prior that just because you are a developer who has a use case that requires this, it is still my computer and you don't get any time on it while you're asking for this.

> Readonly access. Allow an app to read your files but prevent writes or deletes

Again: Absolutely not. There are no files I want your app to have access to without an explanation.

> Allow for negative access (i.e. allow labels or tags on directories to mark them as sensitive and prevent access by default - browsers could do this for their cookie stores, `~/.ssh` could ship with it as a default, etc.)

I know Linux works this way, and it only ever works for stuff that the integrator ships (i.e. on Red Hat, they are called seLinux labels), so it's not something that independent publishers have ever done, and to my knowledge, despite it being so easy, not one independent developer has ever used them in the way you say, despite such a thing being possible for more than 25 years.

> Apple needs to learn to talk to (and listen to) developers.

That sounds like your opinion. I think developers need to explain better what they actually want and why.

You have what you ask for on other platforms, so I think if your ideas were so right you would have simply ignored Apple, so I think Apple doesn't need to do shit for you, and you have some explaining to do.

dvdkon 9 hours ago

All the apps you listed probably work the same on your Mac as they do on an iPhone. If that's the kind of software you're using, then it makes sense you're happy with macOS' current permissions.

MacOS is also used by power users, though. The kind of people who were drawn to it being a user-friendly UNIX and then stayed. I think it's reasonable for them to ask for a more granular permission system that actually supports their usecases.

smilespray 9 hours ago

eviks 7 hours ago

> > Readonly access. Allow an app to read your files but prevent writes or deletes > Again: Absolutely not. There are no files I want your app to have access to without an explanation.

You're a bit confused. The options here are not no access or automatic read only access without an expansion, but full access or read only access (the explanation here is the same and can be arbitrarily bad just like today), so it's strictly an improvement

saagarjha 5 hours ago

> However users are very happy with it.

No, they’re not. They find it really annoying that apps ask them for overbroad permissions

barkerja 5 hours ago

Angostura 4 hours ago

curvaturearth 9 hours ago

Add a user I really dislike apples choices and nag screens which get in the way of me running software

eptcyka 11 hours ago

> I use Spotify, Slack, Zoom, and WhatsApp: All of them have asked for it, but they all seem to work fine if I deny them access to full-disk access. So I am confident your issue is a non-issue for me and millions of people like me.

I use none of these plapps on my Mac, and I've not had issues with the filesystem access APIs.

Xcode has never asked for these permissions though. Pretty sure Xcode *can* read any path in my ~. Without asking.

> I know Linux works this way, and it only ever works for stuff that the integrator ships (i.e. on Red Hat, they are called seLinux labels), so it's not something that independent publishers have ever done, and to my knowledge, despite it being so easy, not one independent developer has ever used them in the way you say, despite such a thing being possible for more than 25 years.

At least I can do it myself via selinux labels or systemd service sandboxing. Apple, the alleged user centrism saints, are yet to provide me with a user-centric way of sandboxing an application. I run browsers and dev shells in microvms on Linux. Those tools get a view of my filesystem that I constrain. Why can't I do the same on macOS? With all the filesystem restrictions they are imposing, they ended up still letting samba read SSH agent UDS - which allowed for a cool vuln where people on your local network could use your SSH keys. Gee, I truly wish those pesky developers actually defined what it is they need upfront so that a user could have a say in how much access these apps get on their system and what data they share.

Apple is the biggest company in the world. They need not your donation of labour.

jwitthuhn 8 hours ago

As a user I continue to dislike Apple presenting security content dishonestly to users, like they do here.

Granting an app full disk access requires clicking "Bypass System Protections", but none of the other permissions do. Apple has not explained what about this one is fundamentally different that it is "Bypassing" instead of "Allowing" like every other permission.

It also doesn't bypass system permissions because you can still only read files readable to your user. In order to scare the user away from using this feature Apple has told a lie.

simondotau 13 hours ago

Developers are important, but Apple understands that it must ultimately prioritise non-technical end users as their highest priority. Apple's approach puts control in users' hands rather than allowing developers to define the scope of access. Moving from Full Disk Access to user-selected folders is a significant security improvement, even if the API doesn't accommodate every developer use case.

It's also critical to recognise that data exfiltration is just as serious a risk as data manipulation. Read-only access doesn't prevent data theft, and time-limited access can't undo it.

SkiFire13 11 hours ago

> it must ultimately prioritise non-technical end users

> puts control in users' hands rather

These two statements are very much at odds with each other.

Non-technical users generally don't know which folder the app needs. It will be confusing for them. If anything this feature works best for *technical* users, that know, or have the ability to look up, which folders the application actually needs.

collabs 10 hours ago

comex 13 hours ago

Apple tried the first thing first. That was App Sandbox, and you can grant access to specific folders through the open dialog (or better yet, use the open/save dialog to access individual files so that no broad permissions are needed at all). But nobody adopted App Sandbox unless forced to.

Negative access is what came next, applied to all apps. By default, an unsandboxed program can access everything except specific protected directories, and can request access to those directories too, e.g. Documents, Desktop, Photos, other apps' data.

Full Disk Access is the last resort that turns all of that off. Or, well, was.

It's also the only way to access Messages, which might be why certain AI apps request it.

semi-extrinsic 9 hours ago

Powerpoint/Word on Mac will pop up a slightly confusing "grant permission to specific folder" dialog if you try to rename the file you are working on. GIMP does not, but somehow needs to be specifically given access to the clipboard, which Powerpoint has by default.

At this point, permissions on Mac is in such a broken state it does not add anything of value. It is extremely common for apps to open up dialog boxes telling you exactly where to go in system settings to grant them access. Malware is just going to do the same, and users are trained to expect it.

mike_hearn 8 hours ago

saghm 3 hours ago

Isn't the entire premise of the system being discussed here is that developers are forced to use it? So then why not just force developers to use the first thing you described?

InsidiousWombat 2 hours ago

Developers are absolutely terrible with APIs like this and will just go the shortest route to get their feature working.

"Don't trust developer" is absolutely the right thing to do here, because developers WILL try to trick user into getting them more access than required

Someone 8 hours ago

> This is a very poorly conceived API

I see it more as a step in the right direction. They could add separate “read only” flags in the future, for example, and add an API for apps to tell this system component to ask the user to give permission for specific directories (time limited already is there, sort-of, it seems, with the option to ask the user each time, which I assume doesn’t mean “on every read or write call”)

Also, AFAIK most user applications never need this. They can have their own store for ‘their stuff’ and standard file dialogs already open up access to files user pick in them.

code_duck 2 hours ago

Your first suggestion, to have the developer specify which folders it needs to access, is already how it works. Hmm... for some reason there is supposed to be a help page called "Control access to files and folders" but it is 404ing right now. Anyhow, I frequently see a newly installed application request access to the Desktop, Downloads, or Documents folders.

noduerme 13 hours ago

I disagree, because I think the default should be no access, then manually checking those folders and whether there may be something in them that you don't want the app to access. How many git repos contain secrets, that you may want to exclude? If you get a popup saying an app wants access to an entire branch of your filesystem, it shouldn't be easy to approve that with a single click, without granularly checking what's in there beforehand.

Many apps already work this way and request access to a single directory, and the best apps (little snitch, arq) give you fine control over what is accessible for what actions.

Bengalilol 7 hours ago

Letting users choose which directories any app can have access to is a great solution. For users and for devs.

Full access is a non sense.

Before, we had to Terminal it, create a user group, chmod this, chmod that, authorize dirs and sub dirs and let it go.

If I can just click dirs directly, I am happy with it (dev and user here).

Angostura 4 hours ago

> Apple needs to learn to talk to (and listen to) developers

In this case, Apple has prioritised the safety of its end users, I think the page is well written and the implementation is reasonable

geraneum 10 hours ago

> Rather than having to have the user select the folder they want to grant access to

To the end user a list of directories like ~/Library/Support… is meaningless. This is a misguided approach.

Jean-Papoulos 10 hours ago

Apple cares about customers, not developpers. Rightly so.

In an perfect world such an API would be great. We don't live there unfortunately

techpression 11 hours ago

As a developer, developers have gotten lazy and shouldn’t be who you listen to primarily these days. Ask any of the harness companies if they’d prefer full access to everything by default and they’d say yes, which is a massive red flag in itself. Apple clearly understands we’re currently in a very bad place and need to enable safer operations for the majority. Moving forward I think we’re going to have to rethink the entire concept of file systems as a static thing and abstract it away into something completely virtual when running software.

duskwuff 13 hours ago

> Allow for negative access (i.e. allow labels or tags on directories to mark them as sensitive and prevent access by default

Apple has already taken some (manual) steps in this direction - certain directories under ~/Library/Application Support are inaccessible to other applications without "full disk access". In particular, web browsers and Discord have this protection applied - this is to thwart some common types of session-stealing malware.

https://wojciechregula.blog/post/golden-gate-appdata-protect...

saghm 2 hours ago

I feel like the entire point of what they were saying is that they want to be able to define the permissions themselves, not just be forced into the default set that Apple defines for non-technical users. Adding additional default rules isn't taking steps in that direction; it's going further in the same direction they were already going in. To completely torture the usual geometric metaphor, moving further along a single axis still increases the drift from the point where they'd like it to be (which is moving along the orthogonal axis as well).

saagarjha 5 hours ago

Yes I’m very glad that people don’t have my Discord memes in public servers and yet my actual sensitive data in a folder I made is sitting around completely exposed

throwawaysoxjje 8 hours ago

Developers having four decades of full disk access has put us in the situation we’re in today.

they can’t be trusted with it.

concinds 8 hours ago

I think Apple should work directly with devs (prioritized by installed base) as part of the solution, because most devs simply don't give a fuck. My DAW requests access to my whole Documents folder, only because it stores support files there. It should store that in its own Containers or App Support folder.

eviks 7 hours ago

Given the level of allergy Apple has towards user empowerment and customization, there is no way they'll be able to do anything remotely similar to the usability you describe

everyone 8 hours ago

The security theatre on mac is insane.

ramijames 5 hours ago

The most annoying thing is that a lot of interesting app ideas are simply disallowed on the App Store because of Apple's closed-minded view of what is appropriate.

postalcoder 15 hours ago

This is a good thing. There are too many apps that request full disk access despite not needing it.

I counted 44* applications on my mac that ask for FDA. I've only granted it to 8. The other apps work just fine without it. (Some apps that ask for full disk access: Anki, a flashcard app and Soulver, a calculator app – cmon now)

This change is less about bureaucracy and more requiring developers to be more clear why it needs the permissions it does.

*edit: originally said 56

david_allison 10 hours ago

> Some apps that ask for full disk access: Anki, a flashcard app

Could you report this: https://github.com/ankitects/anki

----

For historical reasons, the Android app requests "All files access", if not using the Play Store variant. I'm working to fix this.

We don't need it. The replacement API is 300x slower on some phones[1] and is infeasible to use.[0] It should be possible to use AnkiDroid in a "public" folder, but it no longer needs to be the norm. Times have changed

[0] https://news.ycombinator.com/item?id=43987745

[1] just tested: 966ms for a file delete on my Pixel 9 Pro vs 3ms

asimovDev 7 hours ago

i have 8 apps listed under the permission and none were given the said permission. All of these apps work fine , i cannot remember when they even requested it. android studio,m firefox, iterm, phpstorm, siriactionsd, slack, spotify and xcode

solyin 15 hours ago

44? What are you going around and doing‽

Mine are a raspberry pi image flasher, Alfred, my backup software, and ghostty.

(Not saying you're computing wrong, I'm interested in your computer experience, it's just different from mine)

postalcoder 14 hours ago

The requesting apps are broken evenly into these categories:

  - coding agents
  - dev tools
  - browsers and extensions
  - file utilities
  - automation apps
  - media
I think it's less that i'm doing anything egregious and more that the full disk access permissions model has been broken lol.

MBCook 14 hours ago

TeMPOraL 8 hours ago

kergonath 6 hours ago

It’s also a function of how log that computer has been in use. I just checked on mine and there are things I haven’t used in a long time.

concinds 8 hours ago

Not them but here are some: Anki, ChatGPT, Claude, Microsoft AutoUpdate Helper (MS Office), Fission (audio editor like Audacity), Parallels Desktop, WhatsApp.

justauserid 10 hours ago

restic, tarsnap, borg, and kopia – I am planning a way to avoid backing up certain folders (so that FDA won't be needed for these apps; but certain special directory folder permissions will still be needed). Then there are a few objective-see apps, an app-uninstaller app, and a disk analysis app.

Askers? Too many. I have been removing them from there using the "–" button but I feel that might be counter-intuitive as these keep asking and then turning up there anyway. So I will stop doing it now.

kinabalu76 an hour ago

I think Apple is being smart here and people are blowing this way out of proportion for views. The truth is that we've seen people who know how to run secops get hacked, so putting controls to ensure we scare the shit out of people who think giving claude access to their entire disk is no big deal is a great idea.

vbezhenar 15 hours ago

For me more important would be to exclude specific folders from that full disk access (like ~/.ssh), rather than selecting one directory.

For example I've used Daisy Disk app to visualize directory size. It's best used with full disk access. But I know that my `.ssh` is tiny and I'd prefer for this app not to be able to access it at all.

hosteur 8 hours ago

Yeah. And being able to see that a file exists and its metadata like size, modified date, etc. should be possible to grant without granting access to reading the contents of files let alone writing files.

eviks 7 hours ago

What "you'd prefer" is for that app to have full access to metadata instead of the current dumb system that's not granular enough to block reading secrets

charcircuit 7 hours ago

The bigger issue here is your ssh program is not generating and storing the key in the keychain. Storing keys in regular files is not secure.

827a 5 hours ago

I've never felt at odds with the AI zeitgeist influencer sphere more than concerning mac full disk access. It is difficult for me to imagine a situation where I would trust any process with the ability to read and write anything, anywhere, on my disk. There isn't even an Apple-made program I would think should need this permission, except Spotlight.

Isn't it funny that we still call this permission Full Disk Access? We haven't used disks in ages.

[1] https://blog.pragmaticengineer.com/grolk-cli-uploaded-all-yo...

lp92 4 hours ago

The floppy disk used to be the save icon for a long time after floppies went out of main stream use. People will continue to use the same term.

vsgherzi 15 hours ago

This seems like a fine change? I don’t quite understand what the pushback is could someone spell it out for me?

MBCook 14 hours ago

The only complaint I’ve seen is that the full disk access dialog is scary.

Well ok? Full disk access is EVERYTHING. Keys to the kingdom. If it’s not encrypted (and some of Apple’s stuff isn’t that should be) then apps that have the permission can anything.

Before that wasn’t the worst thing in the world, most apps didn’t care. But now we have LLMs. And suddenly people are realizing just how creepy full disk access really is.

So I agree. This is a great change.

Gigachad 14 hours ago

This whole conflict came up because AI companies wanted full disk access so they could go wild on your computer without having to prompt the user for permission.

So it’s Apple who wants to minimise risk and protect the users personal data vs AI companies and enthusiasts who want to let Claude rip on their computer.

comex 13 hours ago

I have Claude and ChatGPT's desktop apps installed and neither has asked me for Full Disk Access. It's Meta whose AI app was, at least allegedly, directing users to enable Full Disk Access in order to access the Messages app.

To be fair, there is/was no way to request access to Messages specifically. And Claude and ChatGPT do both have Messages connectors, but you have to go out of your way to search for them. Presumably the AI itself will also tell you about Full Disk Access if you ask for something that requires it.

(Also, both of those apps do promote 'computer use', i.e. letting the AI remote-desktop your computer, which effectively grants full system control anyway. But at least in that case it's more obvious to the user what's going on.)

hosteur 8 hours ago

xmddmx 4 hours ago

I understand the goal here, but the implementation is quite poor:

- This is being rolled out in the second beta of a .x OS release

- As typical of Apple, there is zero documentation other than vague "things are changing" statements such as this: https://developer.apple.com/news/?id=oqng0zjk

My app specifically needs to monitor mouse events while in the background. It's not clear where that fits in the new security regime - there is an "Input monitoring" entitlement but in the OS it only mentions "keyboard" not mouse.

It really feels like apple is being reactive here - reshuffling the permissions categories on the fly in response to a changing world and slipping these changes into a point release, rather than having a well-designed system built from the ground up.

gregoriol 10 hours ago

It's really annoying that Apple being a gatekeeper with the App Stores can't manage to validate what good/bad apps are allowed to do without having the user tap accept on dozens of popups, most of the users don't even have a slight idea of what each authorisation popup implies, and they shouldn't have to.

mike_hearn 8 hours ago

They do. Almost all permissions you can request from macOS don't have any UI associated with them. You have to statically declare them up front as an entitlement. If shipped outside the App Store the OS grants most entitlements automatically. If in the store, the app reviewers sanity check the entitlements against what the app does.

gregoriol 3 hours ago

Not really though: one of the meanest examples being "Local networks", which you get a popup for on iOS and macOS, but hardly anyone knows what it means.

mike_hearn 2 hours ago

dofm 15 hours ago

Freaking finally!

This looks really well-implemented, considering the complexity of explaining all of this to users.

Elseself 14 hours ago

Why isn't this a filesystem-level permission yet? Like being able to set file and folder access for specific apps like we do for user accounts.

For example I could set my "Top Secret Ideas" folder to "Deny" for "All Apps" but "Read & Write" for Finder and my Markdown editor.

The tricky part would be how to assign IDs or "accounts" for apps and what to do when an app gets updated..

Gigachad 14 hours ago

This is kind of how macOS works and has been trending. It’s why you see prompts when apps try to access files in documents or downloads. But full disk access sidesteps that permissions system.

saagarjha 14 hours ago

> The tricky part would be how to assign IDs or "accounts" for apps and what to do when an app gets updated..

Apple has the infrastructure to handle this already

dmitrygr 15 hours ago

This is great! I loved when iOS let me expose only a subset of my contacts list to whatsapp (and, this is important: banned facebook from retaliating) -- the subset it already knows, and this is another good step in the right direction. I trust precisely 0% of apps with my private data, and apple making it easier to limit exposure is good!

csydas 8 hours ago

yeah i don't get the push back in full (read the comments they land flat)

i like that ios gives option of "give app access to specific picture" instead of carte blanche access to photos, some apps still don't do it and it's a reason to be wary of such apps, and i'm glad it's getting more granular on macos also

nicky0 3 hours ago

This is not just for Full Disk Access but also covers the (formerly known as) Accessibility permission as well

nottorp 9 hours ago

I only worry about one thing: will DaisyDisk still work?

justauserid 10 hours ago

Will this allow me to permit apps only "read" (and/or specific write i.e delete, change) access on chosen directories? Not clear from the article. I'd love it if I can give read-only access to many backup apps I use on specific folders.

Apple had the chance to be granular about directory permissions but it chose rather a mess – there's FDA and then there's also specific folder permissions and they sit separtely. UI adds to that mess – sometimes just by looking at the listing you cann't tell whether the permission is given or not because in "files and folders" permissiosn view it lists FDA if available and greyed and in some cases it doesn't even that app has FDA, and sometimes it lsits that FDA even if that app doesn't have FDA but asked for it. It will be even less sane if there's an app that asked for app data permission and you have many apps installed because now there are those entries for "apps' data directories". It's painful to both users (technical and non-tech nical) and the developers.

I think one of the reasons is Apple is paying the price of closed-source development. Something else is needed? Just add few hundred flags and make it happen one way or the other. Things might break? Well, add flags in other services/platforms as well, after all it's all in-house. User is still facing problems? Well, take them on phone calls, spend a few hours with them over a few calls at various levels of "seniority" (but actually showing no difference at all) and then make them reinstall the OS a few times and then close the case saying their exerience has been noted, without providing any issue/bug number or so. If they still insist? Tell them there's no next level of escalation and maybe possibly give them the option of dropping the device at an Apple centre (in most countries not the Appele stores) and remind them it can take from weeks to months. As a mac user it boggles my mind how unsafe of a ticking time-bomb of an OS we/I are using.

I just wanted to mention that there's a lovely little app called `2.1.278` and they also ask for FDA. I know the version is a bit old, can't seem to keep up :) Haven't moved all that behind containers and sandbox-exec is a bit unwieldy.

scotty79 11 hours ago

Something like that should be a part of any permission system from the start. "The app needs your location." "Sure, give it a fake location, becuase I don't think it deserves my real one."

This app wants to access you name and email address. Sure give it a burner one because I don't think it should have my real one.

This app wants access to your photos. Here give it access to the ones I selected as if they were my whole gallery if it insists on that.

saagarjha 15 hours ago

> Apps that might ask for Full Disk Access or System & App Protection Override include backup apps, disk cleaners, file indexers, security apps, and others.

This is not what Full Disk Access was designed for. Not a huge fan of Apple misrepresenting what permissions do so they can pretend like their policies are consistent and not a kneejerk reaction to what’s going on in the world.

liuliu 15 hours ago

Can you be more specific and educate me / others in this thread what they were designed for? That clarification helps a ton!

saagarjha 15 hours ago

Accessing your files? The first thing people put there is their terminal app.

Gigachad 14 hours ago

geocar 12 hours ago

thatfrenchguy 15 hours ago

what 15 hours ago

em-bee 15 hours ago

what was it designed for then?

saagarjha 15 hours ago

It might be interesting to take a peek at what Apple is using it for, or namely, what exemptions Apple gives themselves. Is Safari a backup app or file indexer? Why does it get to bypass the protections, hmm? (Hint: it has access to your Firefox and Chrome folders.)

khazhoux 14 hours ago

kylehotchkiss 15 hours ago

I'm clearing out my "full disk access" list when this lands and re-granting them all!

rvz 13 hours ago

Good idea, will do the exact same immediately.

AlexandrB 2 hours ago

Features like this should always include a way to fake giving relevant permission in a way that's transparent to the App. For example, for file access it would be nice to be able to redirect the folder the app wants to access to somewhere else.

I'm sure it would drive app developers nuts, but I don't care. I'm sick of apps begging for location, contacts, or photos access before they do anything useful.

villgax 5 hours ago

On iOS, Disney Hotstar app is one blatant violator of App Store guidelines, on random app startup they'll play their video ads at full volume with no option to skip it or mute it, this is despite being a paid subscriber to the OTT app itself. Such nuisance.

jshier 16 hours ago

... on your Mac. New Apple support document about the upcoming full disk access changes.