On an Apple Silicon Mac running macOS 27.0.1 (26A434), I am assessing the arm64 command-line tool age v1.3.2. The downloaded file retains its quarantine attribute.
The command spctl --assess --type execute --verbose=2 returned exit code 1 with: “internal error in Code Signing subsystem”. A later codesign --verify --strict --verbose=4 check returned exit code 0. The file hash and recorded attributes did not change around the strict verification.
The tool is ad-hoc/linker-signed, with no TeamIdentifier. I have not executed the tool or removed quarantine. The exact environment and independent raw output file for the first spctl assessment were not recorded; the error above is a transcription of the observed output.
What is the supported way to assess a standalone command-line tool in this situation? How can I distinguish a policy rejection from an assessment failure, and what further diagnostics would you recommend without running the tool or reducing system security?
Topic:
Code Signing
SubTopic:
General
4
0
242