fix(install): strip macOS Gatekeeper quarantine xattrs (#313)#319
Merged
Conversation
5 tasks
Prebuilt macOS binaries are not Apple-notarized. When a user downloads the `aarch64-apple-darwin` tarball directly (via `gh release download`, browser, or curl), macOS attaches `com.apple.quarantine` and `com.apple.provenance` extended attributes and then kills the binary on first launch with signal 9 — producing `Killed: 9` and **no error output**. This makes the failure look like a cora crash rather than a distribution gap. Changes - install.sh: after `chmod +x`, on macOS run best-effort `xattr -dr com.apple.quarantine` and `xattr -dr com.apple.provenance` on the installed binary. Non-fatal on failure (binary may already be clean). - README: add a prominent <details> block under the Install section explaining the `Killed: 9` symptom, the manual `xattr -dr` workaround for direct-download users, and the `cargo` / Homebrew alternatives. - CHANGELOG entry under `## [0.6.1] -> Fixed — Install (macOS)`. Note: the real fix is Apple notarization (codesign + notarytool), which requires an Apple Developer ID certificate. This PR is the minimum-cost stopgap documented in the issue. A follow-up can add notarization to `.github/workflows/release.yml` once credentials are available. Bump 0.6.0 -> 0.6.1 (patch).
ajianaz
force-pushed
the
fix/313-macos-gatekeeper
branch
from
27f817f to
b43dbaf
Compare
This was referenced Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #313 — macOS binary release killed by Gatekeeper quarantine (
com.apple.quarantine/com.apple.provenance).Prebuilt macOS binaries are not Apple-notarized. When downloaded directly (
gh release download, browser, curl), macOS attaches quarantine xattrs and kills the binary on first launch withKilled: 9and no error output, making it look like a cora crash.Changes
install.shAfter
chmod +x, on macOS run best-effort:Non-fatal on failure (binary may already be clean). Logs
Stripped macOS quarantine attributes (Gatekeeper workaround).README.mdAdded a prominent
<details>block under the Install section explaining:Killed: 9symptom,xattr -drworkaround for direct-download users,cargo/ Homebrew alternatives that sidestep Gatekeeper entirely.CHANGELOG.mdEntry under
## [0.6.1] -> Fixed — Install (macOS).What this does NOT do
The real fix is Apple notarization (
codesign+xcrun notarytool submit) in.github/workflows/release.yml, which requires an Apple Developer ID certificate + App Store Connect API key. This PR is the minimum-cost stopgap explicitly suggested in the issue. A follow-up issue can track notarization once credentials are available — the install.sh strip will remain useful even after notarization (defensive, covers direct-download paths).Tests
sh -n install.sh— syntax OK.cargo build/cargo clippy -- -D warnings/cargo fmt --checkall clean (no Rust changes).Versioning
Patch bump
0.6.0→0.6.1(shares the release with #316 and #312).Cargo.tomlwill conflict with #317 and #318. Suggested merge order: #317 → #318 → this PR. Conflicts are confined to the## [0.6.1]block ofCHANGELOG.mdand the version line inCargo.toml/Cargo.lock.Checklist
cargo buildpassescargo clippy -- -D warningscleancargo fmtappliedsh -n install.shpasses## [0.6.1]→### Fixed — Install (macOS)Cargo.toml+Cargo.lock