summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/tails_server.mdwn
diff options
context:
space:
mode:
author127.0.0.1 <127.0.0.1@web>2016-11-16 12:25:27 +0100
committeramnesia <webmaster@amnesia.boum.org>2016-11-16 12:25:27 +0100
commitb58b617df466c38c9f622831f815e8990480f68f (patch)
tree6c74c5f190eb2d2280773895340dfb09ec2357ac /wiki/src/blueprint/tails_server.mdwn
parent382fbba001c672feaa0b8f626b616d64f8798b0a (diff)
Fix link
Diffstat (limited to 'wiki/src/blueprint/tails_server.mdwn')
-rw-r--r--wiki/src/blueprint/tails_server.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/wiki/src/blueprint/tails_server.mdwn b/wiki/src/blueprint/tails_server.mdwn
index 627b008..f494c41 100644
--- a/wiki/src/blueprint/tails_server.mdwn
+++ b/wiki/src/blueprint/tails_server.mdwn
@@ -15,7 +15,7 @@ Such services are immensely helpful for working together in groups over distance
* It works behind NATs and firewalls
* It limits attack surface
-The Tails Server should be usable via both a graphical user interface (GUI) and a command line interface (CLI). The interfaces would be used from within a running Tails session (in contrast to the design in the [Legacy Blueprint](#index3h1). The CLI solution would make it easy to administrate a Tails Server remotely via SSH.
+The Tails Server should be usable via both a graphical user interface (GUI) and a command line interface (CLI). The interfaces would be used from within a running Tails session (in contrast to the design in the [Legacy Blueprint](https://tails.boum.org/blueprint/server_edition/). The CLI solution would make it easy to administrate a Tails Server remotely via SSH.
Both interfaces should automatically install the services chosen by the user, configure them for the use in Tails and start them. It should be a generic solution which makes it easy to add many different services.
The user should be able to choose: