Remix.run Logo
▲ saagarjha 5 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 5 hours ago | parent | next [-]

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

▲saagarjha 5 hours ago | parent [-]

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

▲Gigachad 3 hours ago | parent | next [-]

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.

▲anon373839 3 hours ago | parent [-]

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.

▲comex 2 hours ago | parent | next [-]

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.

▲anon373839 an hour ago | parent [-]

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.

▲what 3 hours ago | parent | prev [-]

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

▲geocar 2 hours ago | parent | prev | next [-]

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?

▲saagarjha an hour ago | parent [-]

Running tmutil? Pulling an email from the mail database?

▲thatfrenchguy 4 hours ago | parent | prev | next [-]

You don’t need full disk access for terminal.app though

▲chii 3 hours ago | parent | next [-]

surely you need it because doing anything other than just listing your home directory would require more access?

Like installing homebrew stuff.

▲rolosa 3 hours ago | parent | prev | next [-]

ls -l / or even ls -la ~ (because of ~/Library) pops up a request for full disk access.

▲geocar 2 hours ago | parent [-]

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

▲saagarjha 3 hours ago | parent | prev [-]

And yet it is widely granted

▲what 4 hours ago | parent | prev [-]

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

▲saagarjha 3 hours ago | parent [-]

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

▲duskwuff an hour ago | parent [-]

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.

▲em-bee 5 hours ago | parent | prev [-]

what was it designed for then?

▲saagarjha 5 hours ago | parent [-]

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 4 hours ago | parent [-]

You didn’t answer the question.

What apps was it actually designed for, that you say Apple is misrepresenting?

▲saagarjha 3 hours ago | parent [-]

It's clearly designed to make Terminal work

▲geocar 2 hours ago | parent | next [-]

It is not. You said this elsewhere, but it's not true.

https://news.ycombinator.com/item?id=50526560#50528036

▲Liuser 3 hours ago | parent | prev [-]

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.

▲saagarjha 3 hours ago | parent [-]

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.