Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-07-26 08:15:59 -04:00
Code Issues Projects Releases Packages Wiki Activity

Update RSK description to account for minor release keys

Browse source
This commit is contained in:
Andrew David Wong 2023-06-02 17:59:35 -07:00
parent 1376696941
commit a6fedbdd8a
No known key found for this signature in database
GPG key ID: 8CE137352A019A17
1 changed files with 3 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

8
project-security/verifying-signatures.md
View file

@ -294,11 +294,9 @@ Before we proceed, you must first complete the following prerequisite steps:
2. [Import and authenticate the QMSK.](#how-to-import-and-authenticate-the-qubes-master-signing-key) 2. [Import and authenticate the QMSK.](#how-to-import-and-authenticate-the-qubes-master-signing-key)
After you have completed these two prerequisite steps, the next step is to After you have completed these two prerequisite steps, the next step is to
obtain the correct RSK. The filename of the RSK for your Qubes OS release is obtain the correct RSK. The filename pattern for RSKs is
usually `qubes-release-X-signing-key.asc`, where `X` is the [major version `qubes-release-X-signing-key.asc`, where `X` is either a major or minor Qubes
number](https://semver.org/) of your Qubes release. For example, if you were release number, such as `4` or `4.2`. There are several ways to get the RSK for
installing release `1.2.3`, you would replace `X` with `1`, resulting in
`qubes-release-1-signing-key.asc`. There are several ways to get the RSK for
your Qubes release. your Qubes release.
- If you have access to an existing Qubes installation, the release keys are - If you have access to an existing Qubes installation, the release keys are