-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Telegraf for macOS should be signed #8580
Comments
@darinfisher Can you provide any feedback for this? See if there's any overlap with the discussions you're having with the Windows signature stuff? |
So what are the chances of this happening? |
@patgmac We actually have just purchased the certs for this and are just starting to work on getting this implemented in the Telegraf build. |
Great news. I hope by "purchased the certs" that means a "paid Apple developer account" which is required for singing apps, not like a regular cert purchased elsewhere. And being that this would require building on Apple hardware, would this also help with #4801 ? |
@patgmac Yes, the certificates are from our Apple developer account. |
Feature Request
Proposal:
Apple has a hard requirement in current versions of macOS for binaries to be signed and notarized. This FR is to start signing the telegraf binary with a valid Apple certificate and notarize as needed. Here is some documentation from Apple on this topic: https://developer.apple.com/support/code-signing/.
This would ideally mean someone at a company level obtaining an company developer account from developer.apple.com, which is $300/year. Personal accounts could be used at $99/year but the signing would appear in that persons name.
Current behavior:
When running telegraf on macOS Big Sur, the following error messages appear:
Desired behavior:
telegraf should run without error.
Use case:
For continued use of telegraf on the macOS platform, it will need to be signed and notarized.
The text was updated successfully, but these errors were encountered: