-
Notifications
You must be signed in to change notification settings - Fork 1.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
Produce signed binaries #2154
Comments
hmm. I wonder if this is happening because we're not signing the binary when we build it? @dgageot any ideas? |
I'll have a look at this - we can probably get this sorted out with some internal workflows. |
Thank you for the feedback! I'm closing this issue as it's been open a while, and it is not clear if it's still an open issue. No one has recently stated an interest in addressing this, but if you feel strongly about it, please feel free to add a comment or send us a PR! |
This is still an open issue. Nothing has been done about it, I haven't finished setting up a kokoro process for it. |
Closing this issue as we publish signed binaries for windows as of skaffold >= v1.35.1. Please let me know if similar issues are run into |
Information
Steps to reproduce the behavior
Clicked on the link for getting the binary for windows: https://storage.googleapis.com/skaffold/releases/latest/skaffold-windows-amd64.exe
Both the Windows Defender and Symantec Endpoint protection both are prompting me that this .exe can put my system at risk:
The text was updated successfully, but these errors were encountered: