Update qubes-secpack page

* Replace "QSP" with "qubes-secpack"
  (We should only have one official short name for it.)
* Note that the repo itself is independent of the host
  (currently GitHub)
* Minor text cleanup
This commit is contained in:
Andrew David Wong 2016-11-22 14:33:56 -08:00
parent 740aa6d4a4
commit b5aaccb4f3
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17

View File

@ -17,7 +17,7 @@ redirect_from:
Qubes Security Pack Qubes Security Pack
=================== ===================
The **Qubes Security Pack (QSP)** is a Git repository which contains: The **Qubes Security Pack** (`qubes-secpack`) is a Git repository that contains:
* [Qubes PGP keys](https://keys.qubes-os.org/keys/) * [Qubes PGP keys](https://keys.qubes-os.org/keys/)
* [Qubes Security Bulletins (QSBs)](/doc/security-bulletins/) * [Qubes Security Bulletins (QSBs)](/doc/security-bulletins/)
@ -25,17 +25,18 @@ The **Qubes Security Pack (QSP)** is a Git repository which contains:
* [Qubes Bitcoin fund information](https://github.com/QubesOS/qubes-secpack/tree/master/fund) * [Qubes Bitcoin fund information](https://github.com/QubesOS/qubes-secpack/tree/master/fund)
* Security-related information and announcements (e.g., key revocations) * Security-related information and announcements (e.g., key revocations)
The official location of the QSP is: While `qubes-secpack` itself is independent of any particular host, its current
official location is:
`https://github.com/QubesOS/qubes-secpack` <https://github.com/QubesOS/qubes-secpack>
[(link)](https://github.com/QubesOS/qubes-secpack)
History and Rationale History and Rationale
--------------------- ---------------------
On 2013-01-05, Joanna Rutkowska announced the QSP and explained its rationale in On 2013-01-05, Joanna Rutkowska announced the `qubes-secpack` and explained its
an [email](https://groups.google.com/d/msg/qubes-devel/twkOEaMLtNI/lZyGx6_jFCEJ) rationale in an
[email](https://groups.google.com/d/msg/qubes-devel/twkOEaMLtNI/lZyGx6_jFCEJ)
to the Qubes mailing lists: to the Qubes mailing lists:
Hello, Hello,
@ -128,10 +129,10 @@ to the Qubes mailing lists:
How to Obtain, Verify, and Read How to Obtain, Verify, and Read
------------------------------- -------------------------------
The following example demonstrates one method of obtaining the QSP, verifying The following example demonstrates one method of obtaining the `qubes-secpack`,
its contents, and reading them. verifying its contents, and reading them.
1. Clone the QSP repo. 1. Clone the `qubes-secpack` repo.
$ git clone https://github.com/QubesOS/qubes-secpack.git $ git clone https://github.com/QubesOS/qubes-secpack.git
Cloning into 'qubes-secpack'... Cloning into 'qubes-secpack'...
@ -251,9 +252,9 @@ its contents, and reading them.
(The fourth and final lines of output confirm that the two signatures are (The fourth and final lines of output confirm that the two signatures are
good.) good.)
The same procedures can be applied to any directory or file in the QSP. Two The same procedures can be applied to any directory or file in the
methods of verification (signed Git tags and deatched PGP signatures) are `qubes-secpack`. Two methods of verification (signed Git tags and deatched PGP
provided to ensure that the system is robust (e.g., against a potential failure signatures) are provided to ensure that the system is robust (e.g., against a
in Git tag-based verification) and to give users more options to verify the potential failure in Git tag-based verification) and to give users more options
files. to verify the files.