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.
> 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.
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.
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.
Regular users need a way of giving informed consent.
The existing system reminds me of Windows; poorly dialogs designed without any thought for regular users whatsoever, which causes everybody to grant access to everything, as a knee jerk response.
> Regular users need a way of giving informed consent.
This is the unsolved problem. Neither the platforms nor app developers are aligned on solving it between themselves, much less aligned with user interests. My pet peeves:
- Apps requesting way broader or more general access for reasons that are unexplained, whether due to innocent oversight or actual malice.
- Platforms aggressively segregating access into broad categories (to reduce user fatigue), which compounds the problem of broad requests, and then preventing users from being able to override those.
- Platform giving special bypasses to their "valued partners", and refusing to inform the users or give means to disable this access (or grant to apps of their choice).
Now wrt. platforms, I get the arguments and I'm sympathetic, even though most of them don't apply to majority of customers. The end result is still the same: users don't get to offer informed consent, and have little to no control where it actually matters.
> 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.
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.
> 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.
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.
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.
Permissions on macOS work better than any other desktop OS by miles, it's not even close. But the GIMP is not a native Mac app and probably doesn't do things the way it needs to for proper integration. Use Pixelmator or some other Mac graphics app and things work fine.
Apps ask you to manage the system settings dialog only when they're requesting a very high level of system access and ship outside the app store. That describes a lot of apps that developers like to use (custom window managers etc), but not so many apps normal users will encounter.
When apps do uncover use cases that the permissions system isn't a good fit for, Apple are pretty responsive about adapting the system in backwards compatible ways. For example, AI apps wanting full disk access because they want to read the internal files of a messaging app - not ideal, so Apple have introduced a way to grant access to only specific apps from a modal popup triggered when the app tries to do it, not from the system settings app.
The way this is meant to work, by the way, is that the messaging app cooperates with the apps that want access to messages by exposing an app over XPC. AI apps are going offroad because AI companies in such a mad scramble to ship features and because of the complicated web of corporate relationships - does Meta really want to grant OpenAI access to people's WhatsApp messages on macOS or would they prefer to push users towards Meta Muse, etc. So AI apps bypass the genteel cooperative way and try to suck data out of the app's internal files directly. Apple is standing in the middle trying to mediate this stuff in a reasonable way, and I think they're doing a fine job.
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.
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.
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.
> 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.
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.
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
To me, it reads like you're really using 5% of the features offered by each of those apps. Excepting "browsers and extensions", those app categories is basically a shortlist of types of apps that could have a legitimate reason to request full filesystem access.
(That they work fine without full access for your specific needs is positively surprising to me, and very nice.)
I think a lot of apps do it just to avoid all the different prompts. It’s probably easier to get the average person to say yes to that than to have to go through each one over time.
Can I see your documents? Your downloads? Your home folder? Your desktop?
And it’s not like they all happen at once. Every time you go to open a file, it randomly asks you if it’s somewhere they haven’t done it before. Maybe because they’re not using the system open save dialogue, which automatically grants access to that one file.
I like that macOS has these facilities. But the existing dichotomy of all or nothing + 30 prompts just didn’t work well.
That model is still fairly broken, you can ask for all of the specific perms and there is still a ton of stuff that isn't covered and requires full disk access. So even if you want to use all the prompts when needed at time of action, you still cannot as a dev.
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.
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.
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.
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.
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.
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.
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.)
> It's Meta whose AI app was, at least allegedly, directing users to enable Full Disk Access in order to access the Messages app.
What the actual fuck?
A messaging app has no business having full-disk access. I can only assume the real reason for this is to manipulate the user into letting them read files they have no business reading. I would consider that spyware.
How is this not getting them banned from AppStore?
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.
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.
> 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.
I find these permission prompts confusing and maddening, even. Are you saying "access my documents folder" is supposed to mean "grant permission to write any files on my disk"? And if so, what is full disk access supposed to mean? The prompts are all vague and vaguely menacing. I miss when a computer was a computer and not pretending to be a phone.
You misunderstood the parent post. Prompting for the documents folder is one way that "[y]ou can access files without full disk access". With full disk access, you get almost everything.
Though not quite everything. For truly full disk access you need to disable SIP.
Yes, sorry. I did misread that. I thought they were saying there is now an "Allow access to ~/Documents?" prompt that stands for full disk access. I didn't remember seeing anything like that and I know it sounds ridiculous, but I guess it shows how low my expectations are for MacOS lately.
> > 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
Can you explain why an app for backups or indexing don’t need access to your files? I’m really confused what you’re trying to say?
I'm saying that Apple is intentionally picking a limited set of uses that they claim the API is for. Obviously the other options are valid use cases (although most backup apps do not use full disk access in this way, because even with that you miss some data that makes it difficult to restore the machine from).
The page we're looking at is end-user documentation, not policy. Apple is intentionally picking a set of use cases which nontechnical users (the primary targets of the documentation!) are likely to recognize and understand - e.g. "oh, yeah, a disk cleanup utility would need to be able to look at everything to clean it up, wouldn't it". Weird examples like "developer tools" aren't helpful to those users, and would just make the page more confusing.
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.)
Is your issue with Apple not including Terminal and their own apps as examples? I still don’t get what’s wrong with the examples they gave for software needing full disk access.
Yes, because the reason they're doing this is that a bunch of apps are doing things they don't like. They are documenting a bunch of milquetoast usages of this API to draw the line as "if you're not doing this, you are abusing the APIs" when in fact the APIs are used by plenty of other things that they don't really want to talk about, because it makes it less easy to claim that this is some weird rare permission for specialized apps.
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!
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
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.
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.
> 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.
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.
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.
Sure, and power users can grant access.
Regular users need a way of giving informed consent.
The existing system reminds me of Windows; poorly dialogs designed without any thought for regular users whatsoever, which causes everybody to grant access to everything, as a knee jerk response.
> Regular users need a way of giving informed consent.
This is the unsolved problem. Neither the platforms nor app developers are aligned on solving it between themselves, much less aligned with user interests. My pet peeves:
- Apps requesting way broader or more general access for reasons that are unexplained, whether due to innocent oversight or actual malice.
- Platforms aggressively segregating access into broad categories (to reduce user fatigue), which compounds the problem of broad requests, and then preventing users from being able to override those.
- Platform giving special bypasses to their "valued partners", and refusing to inform the users or give means to disable this access (or grant to apps of their choice).
Now wrt. platforms, I get the arguments and I'm sympathetic, even though most of them don't apply to majority of customers. The end result is still the same: users don't get to offer informed consent, and have little to no control where it actually matters.
Add a user I really dislike apples choices and nag screens which get in the way of me running software
> 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.
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.
> 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.
The position is internally consistent. Most apps should never touch the file system outside of their own folder structure that they control.
You can export files to an external location and you can import from external locations in this scheme but they will be user directed.
With this scheme, you would teach most users to select NO!!! if any app asks for full disk access or system access.
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.
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.
Permissions on macOS work better than any other desktop OS by miles, it's not even close. But the GIMP is not a native Mac app and probably doesn't do things the way it needs to for proper integration. Use Pixelmator or some other Mac graphics app and things work fine.
Apps ask you to manage the system settings dialog only when they're requesting a very high level of system access and ship outside the app store. That describes a lot of apps that developers like to use (custom window managers etc), but not so many apps normal users will encounter.
When apps do uncover use cases that the permissions system isn't a good fit for, Apple are pretty responsive about adapting the system in backwards compatible ways. For example, AI apps wanting full disk access because they want to read the internal files of a messaging app - not ideal, so Apple have introduced a way to grant access to only specific apps from a modal popup triggered when the app tries to do it, not from the system settings app.
The way this is meant to work, by the way, is that the messaging app cooperates with the apps that want access to messages by exposing an app over XPC. AI apps are going offroad because AI companies in such a mad scramble to ship features and because of the complicated web of corporate relationships - does Meta really want to grant OpenAI access to people's WhatsApp messages on macOS or would they prefer to push users towards Meta Muse, etc. So AI apps bypass the genteel cooperative way and try to suck data out of the app's internal files directly. Apple is standing in the middle trying to mediate this stuff in a reasonable way, and I think they're doing a fine job.
The security theatre on mac is insane.
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.
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.
Apple cares about customers, not developpers. Rightly so.
In an perfect world such an API would be great. We don't live there unfortunately
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.
> 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.
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.
> 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...
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
> 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
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)
The requesting apps are broken evenly into these categories:
I think it's less that i'm doing anything egregious and more that the full disk access permissions model has been broken lol.To me, it reads like you're really using 5% of the features offered by each of those apps. Excepting "browsers and extensions", those app categories is basically a shortlist of types of apps that could have a legitimate reason to request full filesystem access.
(That they work fine without full access for your specific needs is positively surprising to me, and very nice.)
I think a lot of apps do it just to avoid all the different prompts. It’s probably easier to get the average person to say yes to that than to have to go through each one over time.
Can I see your documents? Your downloads? Your home folder? Your desktop?
And it’s not like they all happen at once. Every time you go to open a file, it randomly asks you if it’s somewhere they haven’t done it before. Maybe because they’re not using the system open save dialogue, which automatically grants access to that one file.
I like that macOS has these facilities. But the existing dichotomy of all or nothing + 30 prompts just didn’t work well.
That model is still fairly broken, you can ask for all of the specific perms and there is still a ton of stuff that isn't covered and requires full disk access. So even if you want to use all the prompts when needed at time of action, you still cannot as a dev.
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.
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.
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.
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.
This seems like a fine change? I don’t quite understand what the pushback is could someone spell it out for me?
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.
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.
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.)
> It's Meta whose AI app was, at least allegedly, directing users to enable Full Disk Access in order to access the Messages app.
What the actual fuck? A messaging app has no business having full-disk access. I can only assume the real reason for this is to manipulate the user into letting them read files they have no business reading. I would consider that spyware.
How is this not getting them banned from AppStore?
Freaking finally!
This looks really well-implemented, considering the complexity of explaining all of this to users.
I only worry about one thing: will DaisyDisk still work?
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..
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.
> 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
I'm clearing out my "full disk access" list when this lands and re-granting them all!
Good idea, will do the exact same immediately.
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.
> 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.
Can you be more specific and educate me / others in this thread what they were designed for? That clarification helps a ton!
Accessing your files? The first thing people put there is their terminal app.
You can access files without full disk access. This is why macOS prompts if you want to allow programs to access your documents folder.
Full disk access is for when you need to make a full disk clone or scan.
I find these permission prompts confusing and maddening, even. Are you saying "access my documents folder" is supposed to mean "grant permission to write any files on my disk"? And if so, what is full disk access supposed to mean? The prompts are all vague and vaguely menacing. I miss when a computer was a computer and not pretending to be a phone.
You misunderstood the parent post. Prompting for the documents folder is one way that "[y]ou can access files without full disk access". With full disk access, you get almost everything.
Though not quite everything. For truly full disk access you need to disable SIP.
Yes, sorry. I did misread that. I thought they were saying there is now an "Allow access to ~/Documents?" prompt that stands for full disk access. I didn't remember seeing anything like that and I know it sounds ridiculous, but I guess it shows how low my expectations are for MacOS lately.
> Are you saying "access my documents folder" is supposed to mean "grant permission to write any files on my disk"?
No? That pretty clearly means read/write any file in your “documents” folder (or whatever folder you selected.
I absolutely do not. I use the terminal without full disk access.
It doesn't stop me from accessing any of my files at all.
What are you doing and why?
Running tmutil? Pulling an email from the mail database?
You don’t need full disk access for terminal.app though
surely you need it because doing anything other than just listing your home directory would require more access?
Like installing homebrew stuff.
ls -l / or even ls -la ~ (because of ~/Library) pops up a request for full disk access.
> ls -l / or even ls -la ~ (because of ~/Library) pops up a request for full disk access.
I just tried all of these on GG 27.2.1: No it does not.
And yet it is widely granted
> > 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
Can you explain why an app for backups or indexing don’t need access to your files? I’m really confused what you’re trying to say?
I'm saying that Apple is intentionally picking a limited set of uses that they claim the API is for. Obviously the other options are valid use cases (although most backup apps do not use full disk access in this way, because even with that you miss some data that makes it difficult to restore the machine from).
The page we're looking at is end-user documentation, not policy. Apple is intentionally picking a set of use cases which nontechnical users (the primary targets of the documentation!) are likely to recognize and understand - e.g. "oh, yeah, a disk cleanup utility would need to be able to look at everything to clean it up, wouldn't it". Weird examples like "developer tools" aren't helpful to those users, and would just make the page more confusing.
what was it designed for then?
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.)
You didn’t answer the question.
What apps was it actually designed for, that you say Apple is misrepresenting?
It's clearly designed to make Terminal work
It is not. You said this elsewhere, but it's not true.
https://news.ycombinator.com/item?id=50526560#50528036
Is your issue with Apple not including Terminal and their own apps as examples? I still don’t get what’s wrong with the examples they gave for software needing full disk access.
Yes, because the reason they're doing this is that a bunch of apps are doing things they don't like. They are documenting a bunch of milquetoast usages of this API to draw the line as "if you're not doing this, you are abusing the APIs" when in fact the APIs are used by plenty of other things that they don't really want to talk about, because it makes it less easy to claim that this is some weird rare permission for specialized apps.
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!
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
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.
... on your Mac. New Apple support document about the upcoming full disk access changes.