251 points by jshier 3 days ago | 128 comments | View on ycombinator
gbdubs 3 days ago |
postalcoder 3 days ago |
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
vbezhenar 3 days ago |
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.
vsgherzi 3 days ago |
kinabalu76 3 days ago |
dmitrygr 3 days ago |
dofm 3 days ago |
This looks really well-implemented, considering the complexity of explaining all of this to users.
gregoriol 3 days ago |
827a 3 days ago |
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...
xmddmx 3 days ago |
- 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.
kylehotchkiss 3 days ago |
Elseself 3 days ago |
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..
undefined 3 days ago |
nicky0 3 days ago |
scotty79 3 days ago |
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.
justauserid 3 days ago |
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.
saagarjha 3 days ago |
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.
AlexandrB 3 days ago |
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.
nottorp 3 days ago |
isjcisjciwndkwn 3 days ago |
How the fuck does Adobe manage to do that when I’ve already denied every single permission under the sun I do not know, but it is absolutely ridiculous that I have no way to stop it and Apple doesn’t seem to care about Adobe’s blatant disobedience and disdain for sane and respectful behaviour.
No, Adobe. My Mac is not yours. You do not get to create folders in my userspace as you see fit.
villgax 3 days ago |
jshier 3 days ago |
ManlyBeachLabs 3 days ago |
SudoSH 3 days ago |
xiaoliangliang 3 days ago |
serifsadi 3 days ago |
ankur_misra 3 days ago |
ManlyBeachLabs 3 days ago |
- 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.