I've been testing code signing outset to whitelist in a Privacy Preferences Policy Control Profile, however code signing outset fails to work. It seems the only way for outset to execute any scripts that trigger a TCC user consent dialog is if the system python interpreter is used in the LaunchAgents and LaunchDaemons. This PR makes the change to the relevant files, and increments the version from 2.0.6 to 2.0.7.
This would then allow any Privacy Preferences Policy Control Profile to whitelist the /usr/bin/python path in order for outset to run.
I've been testing code signing
outsetto whitelist in a Privacy Preferences Policy Control Profile, however code signingoutsetfails to work. It seems the only way foroutsetto execute any scripts that trigger a TCC user consent dialog is if the systempythoninterpreter is used in the LaunchAgents and LaunchDaemons. This PR makes the change to the relevant files, and increments the version from 2.0.6 to 2.0.7.This would then allow any Privacy Preferences Policy Control Profile to whitelist the
/usr/bin/pythonpath in order foroutsetto run.