You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You mentioned in the v0.9.5release notes that you've been using some of the Objective-See code, this works fine for OverSight (defaults read com.objective-see.OverSight) but not BlockBlock so the implementation of preferences in OverSight might help debug this.
The text was updated successfully, but these errors were encountered:
I guess this is because I don't use the "~/Library/Preferences/" folder, while OverSight does. I want to add self-protection later on, so only Shield can modify its own settings, and thus I wanted to keep all files in one place to make it easier. I will defer this until I implement self-protection. Likely not an issue to protect one more location, but will see.
That makes sense, feel free to close this if the two are incompatible.
It would be useful to be able to programatically set the options or set them via an MDM profile but if these are incompatible with self protection then just close this out.
The idea is that I would allow changing settings only through the app. But reading with "defaults read" could still work. I will keep it open for now, and see how it goes.
macOS Version: macOS
11.2
(20D64
)Kernel Version: Darwin
20.3.0
Shield Version:
v0.9.5
User Type: Admin
Terminal Full Disk Access: Yes
SIP: Enabled
Trying to access the Shield preferences via
defaults
using theBUNDLE_ID
&HELPER_BUNDLE_ID
(as defined inConstants.h
) produces the following errorsTo access the Shield preferences you need to use the full path of the preferences file which is
DIR_PATH_ES
+PREFS_FILE
(as defined inConstants.h
).You mentioned in the
v0.9.5
release notes that you've been using some of the Objective-See code, this works fine for OverSight (defaults read com.objective-see.OverSight
) but not BlockBlock so the implementation of preferences in OverSight might help debug this.The text was updated successfully, but these errors were encountered: