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

Ability to disable checksum check #71

Closed
Surgery-Jake opened this issue Dec 16, 2021 · 3 comments · Fixed by #72
Closed

Ability to disable checksum check #71

Surgery-Jake opened this issue Dec 16, 2021 · 3 comments · Fixed by #72

Comments

@Surgery-Jake
Copy link

Surgery-Jake commented Dec 16, 2021

Due to promtail not having support for journald (grafana/loki#1459). I have to build the binary locally and upload to a file server. This means that the checksum part fails when changing promtail_dist_url.

To get around this I added a variable called promtail_check_checksum and replaced

checksum: "sha256:{{ __promtail_checksum }}"
with checksum: "{{ 'sha256:__promtail_checksum' if promtail_check_checksum else '' }}"

I don't know if this is something worth adding as a PR or if I should just leave the role edited locally?

@patrickjahns
Copy link
Owner

Thanks for reaching out.

I very much understand your use-case - one idea/thought at this point: Would it make sense to provide a custom checksum instead of just disabling the check?

One upside could be, that instead of fetching the checksums per default (which is also prone to Man-in-the-middle attacks). One can provide the checksum upfront to ensure that the correct artifact is delivered.
And in your case, you would have the added benefit of being able to also have a bit more "supply-chain" security when you would generate the binaries and checksum them before uploading.

What do you think?

@Surgery-Jake
Copy link
Author

I think that the ability to provide a custom checksum is a great idea. I would be happy to work on it.

@patrickjahns
Copy link
Owner

@Surgery-Jake
Sorry for the delayed response - please feel free to create a PR with that feature - happy to accept it :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants