Skip to content
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

[Bug]: Garden Windows binaries cannot be run because lack of code signing #6730

Open
10ko opened this issue Dec 18, 2024 · 0 comments
Open
Labels
bug ci os/windows priority:high High priority issue or feature

Comments

@10ko
Copy link
Member

10ko commented Dec 18, 2024

Bug

Current behavior

Some Windows users are experiencing issues when updating and trying to run the latest version of Garden.
Some tools (e.g. Crowdstrike) are blocking users from running multiple versions of Garden because the lack of code-signing of the Windows binaries.

Expected behavior

Garden users on Windows should be able to update and run any version of Garden

Reproducible example

Workaround

Updgrade or downgrade to a different Garden version.
Different tools might allow or forbid different versions, we don't have an exhaustive list at the moment.

Suggested solution(s)

Implement code signing in the release pipeline.

Additional context

Related to #4250

Your environment

  • OS:
  • How I'm running Kubernetes:

garden version

@10ko 10ko added bug ci priority:high High priority issue or feature labels Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug ci os/windows priority:high High priority issue or feature
Projects
None yet
Development

No branches or pull requests

2 participants