Skip to content
This repository has been archived by the owner on Nov 4, 2021. It is now read-only.

code signing for OS X #12

Open
edbordin opened this issue May 10, 2020 · 0 comments
Open

code signing for OS X #12

edbordin opened this issue May 10, 2020 · 0 comments

Comments

@edbordin
Copy link
Collaborator

edbordin commented May 10, 2020

On OS X, archives downloaded in the browser are marked with a "quarantine flag" which is transferred to all files when an archive is extracted https://discourse.brew.sh/t/code-signing-installed-executables/2131/12

The user will get a warning for every executable they try to run if this flag is set.

These are the solutions to avoid the warning that I'm aware of:

  • Download with a CLI tool like wget
  • Remove the flag from the archive before extracting with xattr -d com.apple.quarantine
  • Manually allow each executable to run (annoying and probably impractical if changing builds frequently).
  • Code-sign the executables, which should stop the warning appearing at all so long as the developer cert is valid.

I will leave this open for discussion. I'm inclined to say we don't need it but I am not the end user of this build so happy for others to chime in.

EDIT: This behaviour is not new in Catalina so I'm inclined to think users are used to it. But this can stay open for now in case somebody wants to make a case for signing the binaries.

edit 2: windows 10 actually behaves a similar way

@edbordin edbordin changed the title code signing for OS X Catalina? code signing for OS X May 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant