summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/tails_server.mdwn
diff options
context:
space:
mode:
author127.0.0.1 <127.0.0.1@web>2016-04-08 13:32:02 +0200
committeramnesia <webmaster@amnesia.boum.org>2016-04-08 13:32:02 +0200
commit31112709e3adf01c29627a7ba0be4e7500a88eb0 (patch)
tree07d301e2cafa67d9b3613aa4153a110a24439e30 /wiki/src/blueprint/tails_server.mdwn
parent23183c31ea8a5a853394e1fca6abf54e75c8f925 (diff)
Diffstat (limited to 'wiki/src/blueprint/tails_server.mdwn')
-rw-r--r--wiki/src/blueprint/tails_server.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/wiki/src/blueprint/tails_server.mdwn b/wiki/src/blueprint/tails_server.mdwn
index a53c85f..7014cdf 100644
--- a/wiki/src/blueprint/tails_server.mdwn
+++ b/wiki/src/blueprint/tails_server.mdwn
@@ -4,7 +4,7 @@
# Vision #
-The Tails Server should provide a user-friendly way to start onion services that facilitate group collaboration, communication and data sharing.
+The Tails Server should provide a user-friendly way to start onion services in Tails to facilitate group collaboration, communication and data sharing.
Such services are immensely helpful for working together in groups over distance. Usually they are hosted centrally by a third party. This comes with several perils: Users have to trust that the service provider protects their information and does not use it for other purposes or disclose it, and the provider poses as a single point of attack for adversaries. In contrast, a self-hosted onion service comes with several advantages:
@@ -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) which can be used from within a running Tails session. 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: