Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sign Mac Releases for Gatekeeper #115

Open
fjab opened this issue Aug 16, 2021 · 4 comments
Open

Sign Mac Releases for Gatekeeper #115

fjab opened this issue Aug 16, 2021 · 4 comments

Comments

@fjab
Copy link
Contributor

fjab commented Aug 16, 2021

This is something for later, but I just want to mention it here so everyone has heard of it.

MacOS has something called "Gatekeeper", where it only lets you open apps that are signed with a trusted developer ID. As long as we don't have that, new users are greeted with a warning like this:
Screenshot 2021-08-16 at 14 08 14

Anyone who ever used more obscure third party software on Mac knows how to get around this and tell Gatekeeper that there's an exception for this particular app, but I could imagine that e.g. corporate machines don't even allow the user to bypass the check.

From what I see on the Gatekeeper site (above), we might need to be part of Apple Developer program, which costs around 100 bucks per year.

@fjab
Copy link
Contributor Author

fjab commented Aug 16, 2021

Note this technically violates our user story of "no unnecessary hurdles for installation", but given that the MacOS user base is still smaller, I'd ignore it for the moment. What do you think?

@edongashi
Copy link
Member

Hah, of course you must pay an annual fee! How Apple of Apple.

@cristianberneanu
Copy link
Contributor

Yes, code signing (for Mac and Windows) is something that we should address at some point, but I wanted to postpone this discussion for the next iteration, as it involves a lot of complexity and bureaucracy, and it will get very noisy.
Once we add it, it will require constant maintenance from our part (certificates will expire), which is not great in the long term.

@fjab
Copy link
Contributor Author

fjab commented Aug 16, 2021

Yes, agree it's not to be addressed at this point. Just adding it so we have it in front of us.

@cristianberneanu cristianberneanu self-assigned this Sep 8, 2021
@cristianberneanu cristianberneanu removed their assignment Nov 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants