2 ms·
I’m failing to understand the implied outrage here? Permissions have become far more nuanced than traditional UNIX, and can no longer be understood with only ch
by IAmEveryone 7y ago
I’m failing to understand the implied outrage here? Permissions have become far more nuanced than traditional UNIX, and can no longer be understood with only chmod literacy.
Apple doesn’t go out of its way to educate users about these changes because it’s supposed to be as transparent as, say, APFS’s file compression and encryption. HN has nothing but scorn usually for these “un-Professional” users that tend not to spend their time doing binary diffs on new point updates of MacOS housekeeping daemons. They do get a lot more actual work done, though.
The article doesn’t even try to make any specific point how these changes hurt anybody. Indeed the author mentions that nobody would have noticed if not for people running ‘strings’ on new binaries.
Millions of people have been running these changes, none of them even noticed, and all were presumably at least a bit safer than before. People at Apple must be feeling like tourists in bizzarroworld seeing people trying to scandalize this.
- zapzupnz 7y ago> I'm failing to understand the implied outrage here? Because it's entirely manufactured. The writer doesn't seem willing to differentiate file permissions from a sandboxed application's permissions to access the file. Once a sandboxed application is granted permission to access the file system, those file permissions still apply. For non-sandboxed applications, those permissions still apply. For non-GUI applications that run in the command line or as daemons, those permissions still apply. Nothing is inaccurate. There is no lie. File permissions and applications' permissions to escape the sandbox are separate concerns with their own user interfaces (Finder and the Security & Privacy preference pane in System Preferences, respectively). Therefore, the outrage is manufactured.