![]() As a consequence, in the initial release of Catalina, you could drag a file from your desktop into your Terminal, but your Terminal would be unable to access the file. In Catalina, Apple wanted to restrict this. Regardless of whether you opened or dragged in a particular file. ![]() "For years", simply opening an app implicitly gave it access to most of the data on your hard drive. I'm not a fan of what Apple has done in Catalina, but I don't think your take is completely fair. Much more secure! Too bad nobody adopted it. The "proper" solution is/was App Sandbox, where the whole home directory is virtualized, and apps get a whitelist of what they can access rather than a blacklist. In theory you could make the permission correspond to "everything in ~/ except dotfiles and Library", but that would be more confusing. If the application is using a standard OS file open/save dialog, it automatically gets permission to only the files the user chose, without having to grant it blanket Documents and Downloads permission. ![]() In contrast, hardcoding paths within Documents or Downloads is uncommon and considered an antipattern thus, most applications only access Documents and Downloads when the user manually chooses a file within one of those directories. Essentially all applications need to access at least some of those, so you'd have to grant permission to every application you open. There are a lot of hardcoded paths within ~/, including macOS-specific (~/Library/Application Support, ~/Library/Caches, etc.) and Unix-inherited (dotfiles).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |