-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIP on Sierra blocks changes to the accessibility database #51
Comments
Hello hb3b: Here is a workaround the issue... sudo launchctl unload /System/Library/LaunchDaemons/com.apple.locationd.plist |
Hello Ben:
Here is a workaround the issue...
sudo launchctl unload /System/Library/LaunchDaemons/com.apple.locationd.plist
sudo /usr/libexec/PlistBuddy -c "Set :com.apple.locationd.bundle-/System/Library/PrivateFrameworks/AssistantServices.framework:Authorized true" /var/db/locationd/clients.plist
sudo launchctl load /System/Library/LaunchDaemons/com.apple.locationd.plist
Hope this helps
… On Jan 30, 2017, at 12:52 AM, Ben Hecht ***@***.***> wrote:
ERROR: OperationalError: attempt to write a readonly database
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I tried this and it didn't work: Error: Any advice on what to try to resolve this SIP issue would be welcomed. |
Currently, with macOS Sierra, you have a couple options, modify the TCC database booted from another system like during imaging, others are doing this. Or disable SIP temporarily to make changes using like using a NetInstall to disable/enable SIP and make modification to the TCC database when SIP is disabled. I would recommend sending Apple feedback to include the ability to set items like this via Configuration Profiles. |
FYI: Here is one workaround the SIP restrictions, not sure this will work for your environment or system management, but...
Once rebooted, no restrictions will be on the TCC.db even while SIP is enabled. You might be able to create a NetInstall script that does the above steps that could be include in a imaging process. Hope this helps. |
Thank you for the help! |
Note, this workaround might go away in a future OS upgrade. I would recommend filing a radar to support this functionality using a configuration profile. It's because the folder in question is only set one time via rootless.conf and it's not part of the current core to perpetually protected paths. So if you strip the flag post OS install, then it stays stripped. A major or minor OS update in the future can repair/re-set it. |
ERROR: OperationalError: attempt to write a readonly database
The text was updated successfully, but these errors were encountered: