Can't read com.apple.TimeMachine.plist in Mojave

Question

Level 1

91 points

Can't read com.apple.TimeMachine.plist in Mojave

I use a wonderful little, free, still-in-beta app called TimeTracker (https://www.charlessoft.com/). It doesn't work in Mojave because it can't read com.apple.TimeMachine.plist.

There is something very strange about the permissions of this file, which I don't understand. The permissions look perfectly normal, but I am blocked from reading the file (here output from bash):

$ ls -l -@ com.apple.TimeMachine.plist

-rw-r--r-- 1 root wheel 1965 Oct 20 08:18 com.apple.TimeMachine.plist

$ wc com.apple.TimeMachine.plist

wc: com.apple.TimeMachine.plist: open: Operation not permitted

$ cat com.apple.TimeMachine.plist

cat: com.apple.TimeMachine.plist: Operation not permitted

I would like to change something so that read access to this file can be restored, but (a) I can't figure out why I don't have read access, and (b) I am in over my depth in trying change the permissions.

Is it normal to not have read permission for this file? Any thoughts about how to (and whether I should) restore it?

iMac with Retina 5K display, macOS High Sierra (10.13.2)

Posted on Oct 20, 2018 8:33 AM

Reply

Answer 1

aselvan

Level 1

39 points

Oct 21, 2018 6:58 AM in response to alanterra

It appears that Mojave extended SIP (System Integrity Protection) further into users home directory. There are many files and directories that are no longer readable even to root. The only way is to disable SIP which is not a real solution. I am not sure why they find the need for this as this going to create more problem than what it actually solves.

Here are some I found and there are not readable and there could be more.

~/Library/Application Support/CallHistoryTransactions: Operation not permitted

~/Library/Application Support/com.apple.TCC: Operation not permitted

~/Library/Application Support/CallHistoryDB: Operation not permitted

~/Library/IdentityServices: Operation not permitted

~/Library/Messages: Operation not permitted

~/Library/HomeKit: Operation not permitted

~/Library/Mail: Operation not permitted

~/Library/Safari: Operation not permitted

~/Library/Suggestions: Operation not permitted

~/Library/Containers/com.apple.VoiceMemos: Operation not permitted

~/Library/Containers/com.apple.Home: Operation not permitted

~/Library/Containers/com.apple.Safari: Operation not permitted

~/Library/Containers/com.apple.iChat: Operation not permitted

~/Library/Containers/com.apple.mail: Operation not permitted

~/Library/Containers/com.apple.news: Operation not permitted

~/Library/Containers/com.apple.stocks: Operation not permitted

~/Library/PersonalizationPortrait: Operation not permitted

~/Library/Metadata/CoreSpotlight: Operation not permitted

~/Library/Cookies: Operation not permitted

Reply

Answer 2

aselvan

Level 1

39 points

Oct 21, 2018 11:23 AM in response to alanterra

@alanterra,
Actually, I found a way to get around this. You can selectively allow applications to full disk access. Go to "System Preferences" and "Security & Privacy", select "Full Disk Access" on the left and add your app. Note: use caution on which application/command you give permission to full disk access.

Here is what mine looks like.

Reply

Answer 3

alanterra Author

Level 1

91 points

Oct 21, 2018 9:18 AM in response to aselvan

Thank you, aselvan. I agree with your comments. I have to think about whether it is worthwhile to install Mojave — I am thinking not right now. I actually sort of like being able to use third-party software. As Apple says:

Apps that you download from the Mac App Store already work with System Integrity Protection. Other third-party software, if it conflicts with System Integrity Protection, might be set aside when you upgrade to OS X El Capitan or later.

Reply