4 ms·
The average user would be terribly confused by all this and would hardly bother to even analyze requirements that are asked by any app. They will simply allow e
by kumarvvr 6y ago
The average user would be terribly confused by all this and would hardly bother to even analyze requirements that are asked by any app. They will simply allow everything.
More importantly, if they see something like a permissions screen, they will have a false sense of security.
And severe restrictions on the app, would hamper user experience. Code signing and developer ID are the most practical means to ensure quality software.
- angry_octet 6y agoUsers of iOS seem capable of forming nuanced views of the permissions each app should have. I don't see why this shouldn't be done for macos. The problem is 'everything' apps like browsers -- you need to be able to enforce permissions for individual sites. With weak sandboxing we're still left with the problem of LPE -- once you're on the box (with, by default, unlimited network access!) you can gain root quite quickly, because the kernel interface is rather large. So you still need code signing and developer IDs. However dev IDs could be a federated system -- user's shouldn't have to accept Apple as the total and sole authority for accepting or rejecting apps/developers.