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
Description
I am signing an application and then creating a release with Squirrel. When I install the application, the stub executable is not signed but the one within the ‘app-{version}’ directory is signed. I see that Slack’s stub executable is signed and I want to replicate that behavior. Can you explain how to achieve this?
Hello @SultanaJon. Please see the docs on application signing.
My absolute favorite part of open source is checking "under-the-hood". You can see in the source, it creates the stub(s), then signs all files.
I am not a moderator, so if you could close the issue if this resolves your problem, I'd appropriate it.
Squirrel version(s)
v2.0.0
Description
I am signing an application and then creating a release with Squirrel. When I install the application, the stub executable is not signed but the one within the ‘app-{version}’ directory is signed. I see that Slack’s stub executable is signed and I want to replicate that behavior. Can you explain how to achieve this?
Steps to recreate
Expected behavior
The stub executable should be signed.
Actual behavior
The stub executable is not signed.
Additional Information
I have reviewed PR #868 and searched the open and closed issues for my problem.
The text was updated successfully, but these errors were encountered: