suzanne.soy/qubes-doc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Point out that release keys are included in Qubes installations

Browse Source 
QubesOS/qubes-issues#4292
This commit is contained in:
Andrew David Wong 2019-08-18 12:53:10 -05:00
parent b38990e666
commit a93b019bef
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -153,6 +153,10 @@ Now, when you import any of the legitimate Qubes developer keys and Release Sign
The filename of the Release Signing Key for your version is `qubes-release-X-signing-key.asc`, where `X` is the major version number of your Qubes release. The filename of the Release Signing Key for your version is `qubes-release-X-signing-key.asc`, where `X` is the major version number of your Qubes release.
There are several ways to get the Release Signing Key for your Qubes release. There are several ways to get the Release Signing Key for your Qubes release.
- If you have access to an existing Qubes installation, the release keys are available in dom0 in `/etc/pki/rpm-gpg/`.
These can be copied into other VMs for further use.
In addition, every other VM contains the release key corresponding to that installation's release in `/etc/pki/rpm-gpg/`.
- Fetch it with GPG: - Fetch it with GPG:
$ gpg --fetch-keys https://keys.qubes-os.org/keys/qubes-release-X-signing-key.asc $ gpg --fetch-keys https://keys.qubes-os.org/keys/qubes-release-X-signing-key.asc