Post

Replies

Boosts

Views

Activity

Reply to spctl reports internal error for an ad-hoc signed macOS command-line tool
Thank you, Quinn. Yes, we mean FiloSottile’s age, specifically the upstream v1.3.2 darwin-arm64 release. We plan to embed it as a helper and include it in our app’s Developer ID signing, notarization, and distribution process. The existing binary passes strict code-signature verification, while the earlier spctl --assess --type execute returned “internal error in Code Signing subsystem.” We do not regard either result as identifying the cause. We have not established the actual linker invocation used for this upstream artifact. What build evidence would you recommend obtaining to verify Apple linker use, and under what circumstances would you recommend rebuilding this helper rather than retaining the upstream binary for the distribution-signing workflow? We have not executed the helper or changed quarantine or security settings.
Topic: Code Signing SubTopic: General
20h
Reply to spctl reports internal error for an ad-hoc signed macOS command-line tool
Thank you, Quinn. Yes, we mean FiloSottile’s age, specifically the upstream v1.3.2 darwin-arm64 release. We plan to embed it as a helper and include it in our app’s Developer ID signing, notarization, and distribution process. The existing binary passes strict code-signature verification, while the earlier spctl --assess --type execute returned “internal error in Code Signing subsystem.” We do not regard either result as identifying the cause. We have not established the actual linker invocation used for this upstream artifact. What build evidence would you recommend obtaining to verify Apple linker use, and under what circumstances would you recommend rebuilding this helper rather than retaining the upstream binary for the distribution-signing workflow? We have not executed the helper or changed quarantine or security settings.
Topic: Code Signing SubTopic: General
Replies
Boosts
Views
Activity
20h