Skip to content

[FEAT] Binary checksums in GitHub releases #827

@RSully

Description

@RSully

Hi, I am writing automation to deploy Scrutiny and it would be really useful if the GitHub releases included a checksums file. This file could be a simple text file added as an additional asset that lists each file name and their corresponding sha256sum.

This would provide 2 benefits to me: (a) I can validate nothing got corrupt in transit and files were completely downloaded, and (b) I can check a system has the right version of Scrutiny by just checking it's checksum instead of executing it or downloading and comparing locally.

This is particularly helpful for the collector binaries.

I apologize if these exist somewhere already, but I did not see them listed in the GitHub release assets nor release description

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions