From a0b355b0c549b98be3cfa8aea790557a129ef6e8 Mon Sep 17 00:00:00 2001 From: Dave Smith Date: Fri, 16 Jul 2021 21:02:37 -0500 Subject: [PATCH] Move 'properly validated keys' guidance before git verification... ...in the "How to Verify Qubes Repos" section, since you must have properly validated keys before being able to perform a successful `git verify-tag` or `git verify-commit`. --- project-security/verifying-signatures.md | 26 ++++++++++++------------ 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/project-security/verifying-signatures.md b/project-security/verifying-signatures.md index 9625a572..e54b4c28 100644 --- a/project-security/verifying-signatures.md +++ b/project-security/verifying-signatures.md @@ -507,6 +507,19 @@ signed tags or commits on top of them unless you personally vouch for the trustworthiness of the unsigned commits. Instead, ask the person who pushed the unsigned commits to sign them. +You should always perform this verification on a trusted local machine with +properly validated keys (which are available in the [Qubes Security +Pack](/security/pack/)) rather than relying on a third party, such as GitHub. +While the GitHub interface may claim that a commit has a verified signature +from a member of the Qubes team, this is only trustworthy if GitHub has +performed the signature check correctly, the account identity is authentic, the +user's key has not been replaced by an admin, GitHub's servers have not been +compromised, and so on. Since there's no way for you to be certain that all +such conditions hold, you're much better off verifying signatures yourself. + +Also see: [Distrusting the +Infrastructure](/faq/#what-does-it-mean-to-distrust-the-infrastructure) + To verify a signature on a Git tag: ```shell_session @@ -531,19 +544,6 @@ or $ git verify-commit ``` -You should always perform this verification on a trusted local machine with -properly validated keys (which are available in the [Qubes Security -Pack](/security/pack/)) rather than relying on a third party, such as GitHub. -While the GitHub interface may claim that a commit has a verified signature -from a member of the Qubes team, this is only trustworthy if GitHub has -performed the signature check correctly, the account identity is authentic, the -user's key has not been replaced by an admin, GitHub's servers have not been -compromised, and so on. Since there's no way for you to be certain that all -such conditions hold, you're much better off verifying signatures yourself. - -Also see: [Distrusting the -Infrastructure](/faq/#what-does-it-mean-to-distrust-the-infrastructure) - ## Troubleshooting FAQ ### Why am I getting "Can't check signature: public key not found"?