All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.
Go to file
Hans Jerry Illikainen dfd7e5ebe1
Verify the release key with --check-signatures
The original instructions on how to verify the release signing key used
the `--list-sigs` option for gpg.  However, unlike `--check-signatures`,
the `--list-sigs` option does not verify the authenticity of key
signatures.

See gpg2(1):

    --list-signatures
    --list-sigs
        Same as --list-keys, but the signatures are listed too.
        [...]
        Note that in contrast to --check-signatures the key signatures
        are not verified.
        [...]

    --check-signatures
    --check-sigs
        Same  as  --list-keys, but the key signatures are verified and
        listed too.
        [...]

This updates the documentation to use `--check-signatures` instead.
2020-07-03 12:37:48 +00:00
_dev _dev: add explanation 2018-04-18 21:16:59 +02:00
developer added Admin API Fuzzer idea 2020-06-18 17:14:12 +02:00
external Abstract version number 2020-06-18 14:29:27 -05:00
introduction Add section for unofficial chat channels 2020-06-04 09:39:32 -05:00
project-security Verify the release key with --check-signatures 2020-07-03 12:37:48 +00:00
user Update dead link 2020-07-01 06:38:36 -05:00
.travis.yml Update rvm to 2.5 in .travis.yml 2019-12-09 00:00:18 -06:00
CONTRIBUTING.md Fix link 2017-04-04 21:52:06 -07:00
doc.md Fix Markdown syntax and duplicate link 2020-05-18 09:46:53 -05:00
README.md Fix typo 2016-03-22 22:52:54 +00:00

Qubes OS Documentation

Canonical URL: https://www.qubes-os.org/doc/

All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.

For more information about the documentation, including how to contribute, please see the Documentation Guidelines.