Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-02-26 01:31:18 -05:00
Code Issues Packages Projects Releases Wiki Activity

Explain "major version number"

Browse Source 
https://forum.qubes-os.org/t/7027/
This commit is contained in:
Andrew David Wong 2021-10-20 08:42:22 -07:00
parent f380742b08
commit 0cca6ec53d
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -292,8 +292,10 @@ Before we proceed, you must first complete the following prerequisite steps:
The first step is to obtain the correct RSK. The filename of the RSK for your The first step is to obtain the correct RSK. The filename of the RSK for your
Qubes OS release is usually `qubes-release-X-signing-key.asc`, where `X` is the Qubes OS release is usually `qubes-release-X-signing-key.asc`, where `X` is the
major version number of your Qubes release. There are several ways to get the [major version number](https://semver.org/) of your Qubes release. For example,
RSK for your Qubes release. if you were 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.
- 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
available in dom0 in `/etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-*`. These can be available in dom0 in `/etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-*`. These can be