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
Putting into writing what markowsky@ and I have been discussing.
When creating a full Santa release with: with bazel build -c opt --define=SANTA_BUILD_TYPE=release :release and the Santa_dev and Santa_daemon_dev provisionprofiles in the appropriate places, where the provisioningprofiles contain a development certificate, santactl doesn't end up getting signed but everything else does. This of course results in all MOLXPC checks failing with the newly created santactl. Our internal release pipeline inadvertently just codesigns over this generated santactl binary with the correct certificate, so we never ran into this with the actual packaged releases.
The text was updated successfully, but these errors were encountered:
Putting into writing what markowsky@ and I have been discussing.
When creating a full Santa release with: with
bazel build -c opt --define=SANTA_BUILD_TYPE=release :release
and the Santa_dev and Santa_daemon_dev provisionprofiles in the appropriate places, where the provisioningprofiles contain a development certificate, santactl doesn't end up getting signed but everything else does. This of course results in all MOLXPC checks failing with the newly created santactl. Our internal release pipeline inadvertently just codesigns over this generated santactl binary with the correct certificate, so we never ran into this with the actual packaged releases.The text was updated successfully, but these errors were encountered: