On Tuesday, 14 August 2018 at 16:10:41 UTC, Jacob Carlborg wrote:
On Tuesday, 14 August 2018 at 14:42:54 UTC, Seb wrote:
On Monday, 13 August 2018 at 19:09:55 UTC, Jacob Carlborg
wrote:
Any plans for doing the same thing for the installer on
macOS? It complains that it's from an unidentified developer
and forces the user to go into System Preferences and reopen
the installer.
Yes, the certificate allows signing binaries for OSX too.
On macOS the certificate needs to be obtained from Apple
through the developer program [1].
[1]
https://developer.apple.com/library/archive/documentation/Security/Conceptual/CodeSigningGuide/Procedures/Procedures.html#//apple_ref/doc/uid/TP40005929-CH4-SW30
—
/Jacob Carlborg
The say this:
```
Note: Apple uses the industry-standard form and format of code
signing certificates. Therefore, if your company already has a
third-party signing identity that you use to sign code on other
systems, you can use it with the macOS codesign command.
Similarly, if your company is a certificate issuing authority,
contact your IT department to find out how to get a signing
certificate issued by your company. However, while these valid
certificates allow you to sign your code, you can only distribute
through the App Store or through the Developer ID program when
you sign with a certificate issued by Apple.
```
