This is a good thing. There are too many apps that request full disk access despite not needing it.
I counted 56 applications on my mac that ask for full disk access. To those, I've only granted it for 8. The other apps work just fine despite not being granted that permission. (Some apps that ask for full disk access: Anki, a flashcard app and Soulver, a calculator app – cmon now)
Developers must be clear about which permissions it needs for what folders. Part of this change is putting the burden on the developer to be more clear about their permissions model.
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.
> 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.
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.)
This is a good thing. There are too many apps that request full disk access despite not needing it.
I counted 56 applications on my mac that ask for full disk access. To those, I've only granted it for 8. The other apps work just fine despite not being granted that permission. (Some apps that ask for full disk access: Anki, a flashcard app and Soulver, a calculator app – cmon now)
Developers must be clear about which permissions it needs for what folders. Part of this change is putting the burden on the developer to be more clear about their permissions model.
This seems like a fine change? I don’t quite understand what the pushback is could someone spell it out for me?
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.
> 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.
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.)
Freaking finally!
This looks really well-implemented, considering the complexity of explaining all of this to users.
... on your Mac. New Apple support document about the upcoming full disk access changes.