From f14261d4554c3e72463d78c31c73cbb894ec8058 Mon Sep 17 00:00:00 2001 From: Cagebreak Signing Key 1 Date: Sun, 31 May 2020 17:58:26 +0200 Subject: [PATCH] Move signing key section --- README.md | 31 ++++++++++++++++--------------- 1 file changed, 16 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index bf30d62..98b65ee 100644 --- a/README.md +++ b/README.md @@ -107,21 +107,6 @@ Release checklist * [ ] gpg --detach-sign -u keyid release_version.tar.gz * [ ] Upload archive and signature as build assets -### Signing Key - -All releases are signed by at least one of the following collection of -keys. - - * E79F6D9E113529F4B1FFE4D5C4F974D70CEC2C5B - * 4739D329C9187A1C2795C20A02ABFDEC3A40545F - -Should we at any point retire a key, we will only replace it with keys signed -by at least one of the above collection. - -Should we at any point have official mail addresses, their keys will be signed by -a valid key noted above. - -The full public keys can be found in `keys/` along with any revocation certificates. ### Reproducible Builds @@ -179,6 +164,22 @@ For every release after 1.0.5, a GPG signature will be provided in `signatures`. The current signature is called `cagebreak.sig`, whereas all older signatures will be named after their release version. +#### Signing Key + +All releases are signed by at least one of the following collection of +keys. + + * E79F6D9E113529F4B1FFE4D5C4F974D70CEC2C5B + * 4739D329C9187A1C2795C20A02ABFDEC3A40545F + +Should we at any point retire a key, we will only replace it with keys signed +by at least one of the above collection. + +Should we at any point have official mail addresses, their keys will be signed by +a valid key noted above. + +The full public keys can be found in `keys/` along with any revocation certificates. + ### GCC and -fanalyzer Cagebreak should compile with any reasonably new gcc or clang. Consider