58 commits

Author	SHA1	Message	Date
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
Andrew David Wong	8b6979fd34	Recommend using gpg2 with keyserver options instead of gpg ... Closes QubesOS/qubes-issues#5404	2019-10-23 01:05:50 -05:00
Andrew David Wong	f32c81fab1	Recommend gpg rather than gpg2 due to 2.2.17 changes ... Closes QubesOS/qubes-issues#5404	2019-10-20 21:38:13 -05:00
Andrew David Wong	90dc5a26c8	Link to section on copying from dom0	2019-08-18 12:59:33 -05:00
Andrew David Wong	a93b019bef	Point out that release keys are included in Qubes installations ... QubesOS/qubes-issues#4292	2019-08-18 12:53:10 -05:00
Andrew David Wong	b38990e666	Point out that the QMSK is already in every Qubes domU ... QubesOS/qubes-issues#2544	2019-08-18 12:32:44 -05:00
Andrew David Wong	43a39e35b9	Use default doc layout for project security docs	2019-05-26 20:04:23 -05:00
Andrew David Wong	d31c786942	Reorganize files to account for new "External" section ... QubesOS/qubes-issues#4693	2019-05-26 19:32:45 -05:00

Renamed from security-info/verifying-signatures.md (Browse further)