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
In which scenario would this be useful? HTTPS (and TCP...) already checks integrity + authenticates the server. If the worry is the repository getting compromised, then any hashes on the repository would be equally untrustworthy as the binaries.
(If it's to check whether a local file claiming to be ReaPack is an official binary, then you can already do that by comparing against the real ones.)
Perhaps adding detached GPG signature files to the release assets would be a better way of proving not only integrity but also authenticity?
Could the expected SHA512 hash of the archives of the precompiled Reapack binaries be listed on the repository to ensure package integrity? Thanks.
The text was updated successfully, but these errors were encountered: