Codesign binary

[alicerunsonfedora]

Specifications

• Seaglass Version: Version 0.0.520-f697a8c
• macOS Version: 10.14.2 (Mojave)

Expected Behavior

Application opens and is digitally signed.

Actual Behavior

Gatekeeper blocks application from running due to lack of a code signature.

Steps to Reproduce the Problem

1. Download Seaglass
2. Open Seaglass

Do we have an estimate on when we'll be able to see code-signed versions of Seaglass?

[aaronraimist]

I’m not sure when Neil is planning on becoming a developer. I would assume probably not until there is a 1.0 release.

I could sign it now but I’m not sure how the transition from one developer to another works.

You can still open it now by right clicking and selecting open the first time you open it. After that it will work normally.

[alicerunsonfedora]

I'm not sure how transferring works either, but I think you need to make a group or something. If I knew a lot about it, I could probably sign it myself since I code-sign for Termina.

[aaronraimist]

Sparkle says

If you are code-signing your application via Apple’s Developer ID program, Sparkle will ensure the new version’s author matches the old version’s. Sparkle also performs basic (but not deep) validation for testing if the new application is archived/distributed correctly as you intended.

but it looks like it would be possible to transfer it

If you both code-sign your application and include a public EdDSA key for signing your update archive, Sparkle allows issuing a new update that changes either your code signing certificate or your EdDSA keys. Note however this is a last resort and should only be done if you lose access to one of them.

[aaronraimist]

https://circleci.com/docs/2.0/ios-codesigning/