f32a91d793
crates/horizon-release-sign signs a release's checksums with an Ed25519 key that exists only as a secret of the `release` environment, and checks them as launchers will, against the public keys built in from release-keys.txt. Dry runs sign with a throwaway key. Until release-keys.txt lists a key, releases keep going out with SHA256SUMS alone and a warning; once it does, a missing or unknown key fails the release before anything is published. tools/ci/new_release_key.sh pipes a new key straight into the secret and prints only the public key. ring and base64 are already in the lockfile. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
16 lines
430 B
TOML
16 lines
430 B
TOML
[package]
|
|
name = "horizon-release-sign"
|
|
version = "0.1.0"
|
|
edition.workspace = true
|
|
license.workspace = true
|
|
rust-version = "1.85"
|
|
description = "Signed release checksums: release.yml signs SHA256SUMS, the launcher and horizon-server check them before installing"
|
|
|
|
[dependencies]
|
|
# Ed25519 and SHA-256, already in every build through rustls (ureq's TLS): no new crypto code.
|
|
ring = "0.17"
|
|
base64 = "0.22"
|
|
|
|
[lints]
|
|
workspace = true
|