-
Notifications
You must be signed in to change notification settings - Fork 697
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
updated xenial prep instructions with review feedback
- Loading branch information
1 parent
c19181f
commit 36c8c88
Showing
2 changed files
with
11 additions
and
4 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,7 +23,11 @@ Each of these steps are described below. | |
Checking your Server Securedrop version | ||
--------------------------------------- | ||
|
||
The simplest way to check your SecureDrop version is to load the .onion address of your Source Interface in the Tor Browser. The version number will be in the footer of the Source Interface. You can also check the application version from the command line on the *Application Server* by running the command: | ||
The simplest way to check your SecureDrop version is to load the .onion address of your Source Interface in the Tor Browser. The version number will be in the footer of the Source Interface. | ||
|
||
.. image:: ../images/sdsource.png | ||
|
||
If you have already confirmed that you have :ref:`SSH access <verify_ssh_access>` to the servers, you can also check the application version from the command line on the *Application Server* by running the command: | ||
|
||
.. code:: sh | ||
|
@@ -102,7 +106,8 @@ Please verify that each character of the fingerprint above matches what is on th | |
git checkout 0.11.0 | ||
Important: If you see the warning ``refname ‘0.11.0’ is ambiguous`` in the output, we recommend that you contact us immediately at [email protected] (GPG encrypted). | ||
.. important:: | ||
If you see the warning ``refname ‘0.11.0’ is ambiguous`` in the output, we recommend that you contact us immediately at [email protected] (GPG encrypted). | ||
|
||
Finally, run the following commands: | ||
|
||
|
@@ -134,6 +139,8 @@ Open a terminal and run the following commands to install the SecureDrop app cod | |
cd ~Persistent/securedrop | ||
git tag -v 0.11.0 | ||
.. note:: | ||
The SecureDrop application code must be installed in the `~/Persistent/securedrop` directory in order to complete the reprovisioning process successfully. Do not install it in a different location. | ||
|
||
The output should include the following two lines: | ||
|
||
|
@@ -170,12 +177,12 @@ Next, copy the files that you’ll need for the new *Admin Workstation*. Open a | |
cp /media/amnesia/TailsData/openssh-client/* ~/.ssh/ | ||
export SRC="/media/amnesia/TailsData/install_files/ansible_base" | ||
export DST="~/Persistent/securedrop/install_files/ansible-base" | ||
export DST="~/Persistent/securedrop/Persistent/securedrop/install_files/ansible-base" | ||
cp $SRC/{app,mon}* $DST/ | ||
cp $SRC/prod-specific.yml $DST/ | ||
# Next, you’ll need to copy over the instance’s submission key and OSSEC | ||
# Next, you’ll need to copy over the instance’s submission public key and OSSEC | ||
# public key. Their filenames may vary, but you can check them in the | ||
# instance configuration file using the following command: | ||
|