Hello Nordic support,
We are preparing a build-only NCS2.9.0 environment on an Apple Silicon Mac,
macOS26.5.1 (25F80), with commands run in a managed workspace execution context.
We have not installed the SDK globally or interacted with a device. Please help
identify whether the following is a release-signing issue or an Apple native
trust-evaluation/environment requirement, and provide a supported resolution.
Official artifacts and SHA256:
1. files.nordicsemi.com/.../nrfutil
5263376bytes; 1b993eece5a6e3e079ce25fa31a134ce4c12fb51735d10114a2ea4a1df048591
2. Documented macOS universal distribution:
files.nordicsemi.com/.../nrfutil
11669520bytes; 866a0d9e6c8b7b3d46b219caa71e485b26bad3f53c9ba7c06d9665620f35b394
3. Core8.2.1 archive:
files.nordicsemi.com/.../nrfutil-aarch64-apple-darwin-8.2.1.tar.gz
2851838bytes; 3162977182e1fe712dff1ab353de0471dfd63d2d9b7d4cc197d2c77987a959cc
Its extracted executable is5842128bytes; b7ccd9f4931df7168cb590d1129c7c6aed5bf3ae74ad61a43385da7f5544a8b5.
Each download matches its publisher X-Checksum-Sha256 header. Native
`codesign --verify --strict --verbose=2 <file>` failed for thin launcher/core;
`codesign --verify --strict --all-architectures --verbose=2 <universal-file>`
failed for the separately downloaded documented distribution:
```
invalid signature (code or signature have been modified)
In architecture: arm64
```
`codesign -d --verbose=4` reports TeamIdentifier=P3R8YQEV4L,
Runtime Version=15.4.0 and Authority=(unavailable). The universal identifier is
nrfutil; thin launcher identifier is nrfutil-6a9af0aeb8524516; core identifier is
nrfutil-02827a208af5b922. The universal arm64 slice is identical to the thin
launcher before the signature region and has a different signature region.
Static checks of the thin launcher/core found no CodeDirectory page-hash or
special-slot mismatches. LibreSSL3.3.6 detached CMS mathematical verification
succeeded with certificate trust deliberately out of scope; this does not
establish native Apple trust. Embedded leaf subject is Nordic Semiconductor ASA,
teamP3R8YQEV4L, leaf fingerprint
BF1CBD20095FEC418AFBDD2A426D640B55003FBE625A52314B4E8DF18FE83C1A.
Leaf/intermediate dates are valid at inspection (2026-09-16), expiring2027-02-01.
Embedded root matches Apple's published macOS26 root fingerprint. Generic offline
X.509 verification cannot handle Apple's critical certificate extension; no
claim is made that this is the native failure's cause. Timestamp/revocation and
the managed environment's native trust evaluation remain unverified.
The original launcher was invoked once with --help before signature inspection;
bootstrap failed because the restricted context could not resolve the server.
After the signature findings none of these binaries was executed. Core and
universal files were never executed. No re-signing, trust modification,
quarantine removal, alternate-platform execution or security override was used.
Can you confirm the signing/notarization status of these exact release hashes
and advise a supported remedy or a verifiable replacement? If host diagnostics
are needed, please specify the minimal non-mutating checks and expected result.
We are not seeking a way to bypass signature verification.
