Skip to content

v0.9.4

Choose a tag to compare

View all tags
@Gajesh2007 Gajesh2007 released this 15 Sep 18:39
· 1744 commits to master since this release
v0.9.4
605651b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Provider v0.9.4 (Swift CLI)

App Attest recovery, stable machine identities and shadow rollout readiness. Existing MDM/APNs remain authoritative; production App Attest checks remain paused.

v0.9.4 — App Attest recovery and safe shadow rollout

  • Fix the released 0.9.3 App Attest callback-timer abort. Require the callback completion/expiry smoke in the optimized signed bundle, installer and updater; distinguish callback failures from Metal failures.
  • Keep App Attest off by default, require an explicit stable account cohort and provider 0.9.4 or newer. Existing APNs/MDM serving and the supported macOS floor remain unchanged. Production App Attest remains paused until a separately approved rollout.
  • Retry transient shadow failures, including temporarily saturated control-lane sends, without disconnecting serving providers; bound actual uncancellable Apple operations and fence late callbacks.
  • Recover cached enrollment receipts through a separately validated renewal path, retain original failure records, and reconcile interrupted evidence without advancing counters. Receipt renewal requires the dedicated server credentials.
  • Associate machine identities through fresh account-bound App Attest assertions, including reconnects after legacy-key rotation. This does not rewrite balances or certify physical-device uniqueness.
  • Negotiate App Attest protocol 3 to bind app-measured machine model, RAM, CPU/GPU counts and the existing verification key to the signed transcript. Preserve old transcripts and cached enrollment recovery across upgrades; move the unchanged base-reward memory-cap catalog out of the MDM package.
  • Record versioned prospective authorization outcomes, revocation, current-connection freshness, qualified builds and receipt/risk readiness. The private dashboard shows exact cohort denominators and blockers for a later MDM retirement.
  • Capture SDK 27 Apple-signed CodeDirectory measurements and require an exact qualified binary/code-hash pair for prospective build approval. Release builds and their provider tests select SDK 27 / Swift 6.4 and record the full CodeDirectory SHA-256; missing or unsupported measurements stay unknown. macOS can identify the exact code without a bundle-version extension.

Artifact verification

  • Binary SHA-256: 9b4bc81a085977855add2ddcb720e2f09b7e05e5964940ba0033612ccbe265fc
  • CodeDirectory SHA-256: 5ef29c0297d6102a27dfa7112edc0c8e87cea9650fb17afb3fafd2fea4ca528e
  • Bundle SHA-256: a3ac248869f08b2f066faa85f6fabc5792750160567866f0621422b7bd22fbae
  • Metallib SHA-256: 1b3a3b255b581b19ccdada4d778aaabdcbcceeb0a379008214c75414cca84569
  • Signed by: Developer ID Application: Eigen Labs, Inc. (SLDQ2GJ6TL)
  • Apple notarization: accepted.
  • Build, release-SDK tests, signing, notarization and R2 upload passed in run 35003258659. Registration initially failed because the coordinator HTTPS certificate expired. After repairing TLS, publication was completed using the identical uploaded bundle, with its hashes verified again; no rebuild was used.

Install

curl -fsSL https://api.darkbloom.dev/install.sh | bash

What's Changed

  • App Attest 0.9.4: recover safely and prepare MDM retirement by @Gajesh2007 in #1058

Full Changelog: v0.9.3...v0.9.4

Contributors

Gajesh2007
Assets 3
Loading