logoalt Hacker News

If an App Asks for Full Disk Access or System and App Protection Override

221 points • by jshier • today at 2:17 AM • 114 comments • view on HN

Comments

gbdubs • today at 5:14 AM

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.

➕ show 18 replies
postalcoder • today at 3:33 AM

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

➕ show 3 replies
kinabalu76 • today at 5:23 PM

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 • today at 3:36 AM

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.

➕ show 3 replies
827a • today at 1:59 PM

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...

➕ show 1 reply
vsgherzi • today at 3:25 AM

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

➕ show 2 replies
xmddmx • today at 2:24 PM

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 • today at 8:20 AM

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.

➕ show 1 reply
dofm • today at 3:36 AM

Freaking finally!

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

Elseself • today at 4:28 AM

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..

➕ show 2 replies
dmitrygr • today at 3:51 AM

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!

➕ show 1 reply
nicky0 • today at 4:01 PM

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

nottorp • today at 9:22 AM

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

justauserid • today at 8:51 AM

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 • today at 7:08 AM

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 • today at 3:04 AM

> 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.

➕ show 2 replies
kylehotchkiss • today at 3:59 AM

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

➕ show 1 reply
AlexandrB • today at 5:02 PM

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 • today at 1:43 PM

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 • today at 2:17 AM

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

➕ show 1 reply
ankur_misra • today at 3:38 PM

[flagged]

serifsadi • today at 12:58 PM

[flagged]

SudoSH • today at 4:46 AM

[flagged]

xiaoliangliang • today at 3:28 AM

[flagged]

ManlyBeachLabs • today at 6:50 AM

[flagged]

ManlyBeachLabs • today at 6:52 AM

[flagged]