{"id":28178,"date":"2020-02-18T15:40:21","date_gmt":"2020-02-18T20:40:21","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=28178"},"modified":"2020-12-31T16:43:54","modified_gmt":"2020-12-31T21:43:54","slug":"catalina-data-protections-break-file-sharing","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/02\/18\/catalina-data-protections-break-file-sharing\/","title":{"rendered":"Catalina Data Protections Break File Sharing"},"content":{"rendered":"

WillyC<\/a>:<\/p>\n

\n

The new data protections in Catalina make some folders inaccessible by default (for example the ‘Documents’ folder). When an application tries to access one of these folders the OS presents the user with a dialog box to ensure they intended the access.<\/p>\n

This seems to have had the effect of breaking home folder network shares. If you enable file sharing in macOS, any registered user is able to access their home folder using their own credentials. This works in Catalina, but the special private folders (Documents, Downloads, Desktop) can’t be interacted with. Attempts to interact with them result in an ‘access denied’ error and no dialog is presented to the user on the server machine that would allow access. On the client machine, in both Finder and Terminal these folders simply appear empty and you get a permissions error if you attempt to create a file.<\/p>\n<\/blockquote>\n

You log into your Mac with file sharing but can’t access your own folders. The server Mac doesn’t prompt to allow access, and there doesn’t seem to be a way to manually grant it. I found that sometimes toggling file sharing off and then on again helps. But this may not be easy to do while you’re sitting at the client Mac. And the problem eventually comes back.<\/p>\n\n

Previously:<\/p>\n