Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Make it clearer that key generation must be done on the SVS #4249

Merged
merged 1 commit into from
Mar 8, 2019
+10 −1
Merged

[docs] Make it clearer that key generation must be done on the SVS #4249

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion docs/generate_securedrop_application_key.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,16 @@ of this key is only stored on the *Secure Viewing Station* which is never
connected to the Internet. SecureDrop submissions can only be decrypted and
read on the *Secure Viewing Station*.

We will now generate the *SecureDrop Submission Key*.
We will now generate the *SecureDrop Submission Key*. If you aren't still
logged into your *Secure Viewing Station* from the previous step, boot it using
its Tails USB stick, with persistence enabled.

.. important:: Do not follow these steps before you have fully configured the
*Secure Viewing Station* according to the :doc:`instructions <set_up_svs>`.
The private key you will generate in the following steps is one of the most
important secrets associated with your SecureDrop installation. This procedure
is intended to ensure that the private key is protected by the air-gap
throughout its lifetime.

Create the Key
--------------
Expand Down