You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
I have used gon to do signing and notarization for a command line tool. It works correctly when the binary is invoked from the command line (i.e., inside the Terminal application). If a user tries to invoke the tool inside Finder, he sees the same security warning as if the binary where not signed.
After doing some research, I am wondering if the lack of an embedded Info.plist file is contributing to this behavior. Has anyone else tried to ship a signed command line tool and encounter this behavior?
The gon.hcl file contains a bundle_id, but it does not include a Bundle name. Is gon including these (along with a Bundle Version)?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have used
gon
to do signing and notarization for a command line tool. It works correctly when the binary is invoked from the command line (i.e., inside the Terminal application). If a user tries to invoke the tool inside Finder, he sees the same security warning as if the binary where not signed.After doing some research, I am wondering if the lack of an embedded
Info.plist
file is contributing to this behavior. Has anyone else tried to ship a signed command line tool and encounter this behavior?The
gon.hcl
file contains abundle_id
, but it does not include a Bundle name. Isgon
including these (along with a Bundle Version)?The text was updated successfully, but these errors were encountered: