logoalt Hacker News

geocar • today at 5:55 AM • 6 replies • view on HN

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


Replies

dvdkon • today at 9:07 AM

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.

➕ show 1 reply
saagarjha • today at 1:27 PM

> However users are very happy with it.

No, they’re not. They find it really annoying that apps ask them for overbroad permissions

➕ show 2 replies
eviks • today at 11:51 AM

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

You're a bit confused. The options here are not no access or automatic read only access without an expansion, but full access or read only access (the explanation here is the same and can be arbitrarily bad just like today), so it's strictly an improvement

curvaturearth • today at 9:52 AM

Add a user I really dislike apples choices and nag screens which get in the way of me running software

eptcyka • today at 7:42 AM

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

jwitthuhn • today at 10:42 AM

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.