Flipper: Provide signed builds

[pardom]

🐛 Bug Report

The security policy at my company requires apps to be signed and we, therefore, cannot use Flipper.

Could you add signing to your release process?

[passy]

Sorry, at the moment we don't have a way of doing that as the build process happens as part of a GitHub Action in public.

[pardom]

I'm not very familiar with app signing, but I've used GitHub secrets to sign Maven artifacts for publishing. I did a quick search for app signing with GitHub actions and found this:

https://medium.com/better-programming/indie-mac-app-devops-with-github-actions-b16764a3ebe7
https://github.com/bacongravy/mac-app-devops-demo

Perhaps you've already explored these actions and found them not to work. Can you share the efforts you've made toward app signing so the community can offer assistance? I'd be glad to contribute so that I can continue using Flipper daily at work.

[ColtonIdle]

@pardom what happens if you right click the file and press open. Does it give you the option to "open and accept security risk" that way?

[pardom]

@ColtonIdle No, that option is not available to me.

[hsavit1]

I agree - not having signed builds is a significant impedance to upgrading

The Flipper team needs to figure out the upgrade process if it wants everyone involved to contribute to building a better product

[stale[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[renchap]

With Github environments you can now have signing secrets stored in Github and only readable for the production release workflow, which can only be launched by an approved person (so they can check all is legit and nobody changed the workflow to leak those secrets): https://docs.github.com/en/actions/reference/environments

[henryzx]

Noticed that current flipper upgrade pace become more and more frequent.
It becomes a problem now, for that I have to do a manual routine to move flipper out from quarantine each time.
Really looking forward to solve this problem. @passy

[aforty]

I've honestly learned to just ignore Flipper updates because of how painful it is to upgrade an app that isn't signed.

[passy]

Sorry for making this so difficult for you, folks. We don't have a good solution for this right now. We will likely pick this up in Q3/Q4 depending on where Apple is with M1 MBPs which only run signed code (without Rosetta 2). Right now, internally we cannot sign our code at all because it breaks incremental updates.

If someone wants to look into the steps that would be necessary to sign as part of a GitHub Action though, I'd be happy to take a look at any PRs on that front.

[andreialecu]

There are full instructions on how this could be done as part of github actions here if anyone wants to try implementing it: https://localazy.com/blog/how-to-automatically-sign-macos-apps-using-github-actions

Looks pretty simple.

[troy-lamerton]

I would like to share Flipper with the rest of my team. This is blocking me because there's no way I can give something that encourages you to trash it on first launch.

See screenshot: