Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'dksmiffs-master'

Browse Source
This commit is contained in:
Andrew David Wong 2021-07-19 10:35:13 -07:00
commit 649babd88c
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
1 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
project-security/verifying-signatures.md
View File

@ -498,15 +498,28 @@ can be confident that these hash values came from the Qubes devs.
## How to Verify Qubes Repos ## How to Verify Qubes Repos
Whenever you use one of the [Qubes repositories](https://github.com/QubesOS), Whenever you use one of the [Qubes repositories](https://github.com/QubesOS),
you should verify the PGP signature in a tag on the latest commit or on the you should use Git to verify the PGP signature in a tag on the latest commit or
latest commit itself. (One or both may be present, but only one is required.) on the latest commit itself. (One or both may be present, but only one is
If there is no trusted signed tag or commit on top, any commits after the required.) If there is no trusted signed tag or commit on top, any commits after
latest trusted signed tag or commit should **not** be trusted. If you come the latest trusted signed tag or commit should **not** be trusted. If you come
across a repo with any unsigned commits, you should not add any of your own across a repo with any unsigned commits, you should not add any of your own
signed tags or commits on top of them unless you personally vouch for the 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 trustworthiness of the unsigned commits. Instead, ask the person who pushed the
unsigned commits to sign them. 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: To verify a signature on a Git tag:
```shell_session ```shell_session
@ -531,19 +544,6 @@ or
$ git verify-commit <commit ID> $ git verify-commit <commit ID>
``` ```
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 ## Troubleshooting FAQ
### Why am I getting "Can't check signature: public key not found"? ### Why am I getting "Can't check signature: public key not found"?