summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
author127.0.0.1 <127.0.0.1@web>2016-11-16 12:39:28 +0100
committeramnesia <webmaster@amnesia.boum.org>2016-11-16 12:39:28 +0100
commit794bcfc623a99aed278c5e3dc8b231aacc111a46 (patch)
treea975090f9ed62aedc3ba537a8695c9b695807a1c
parentb58b617df466c38c9f622831f815e8990480f68f (diff)
Rephrasing
-rw-r--r--wiki/src/blueprint/tails_server.mdwn17
1 files changed, 9 insertions, 8 deletions
diff --git a/wiki/src/blueprint/tails_server.mdwn b/wiki/src/blueprint/tails_server.mdwn
index f494c41..d39875f 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.
+Tails Server should provide a user-friendly way to start onion services that 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,26 +15,27 @@ 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](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.
+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 Tails Server remotely via SSH.
+Both interfaces should make it easy for the user to install and configure services, and automatically configure the services for the use in Tails. It should be a generic solution which makes it easy to add many different services.
-The user should be able to choose:
+In addition to service specific options, the user should be able to choose:
* Whether the server's configuration and data and the onion service's keys and address are stored persistently (i.e. being restored after reboot) or not.
* Whether the service is supposed to automatically start after booting Tails.
+* Whether it should allow connections from localhost
* Whether it should allow connections from the local area network (LAN).
-In order to achieve this, the following problems have to be solved:
+In order to achieve this vision, the following problems have to be solved:
* Design an extendible and robust format describing the services and how they integrate into Tails.
* Installing the server software.
-* Settings up the onion service, reusing an existing onion address and keys, if chosen by the user.
+* Setting up the onion service, reusing an existing onion address and keys, if chosen by the user.
* Persistently storing the data, configuration, and onion service data.
* Integrating into Tails' firewall.
* Presenting the onion address and client credentials to the user in a way that s/he can easily share them with clients.
* Implementing a proper CLI and GUI to configure and activate services.
-## List of services to implement ##
+## List of services which could be nice if integrated in Tails Server ##
Please add to this list!
* Collaborative text editor
@@ -75,7 +76,7 @@ The GUI will call the service executables with specific arguments and parse the
# Implementation #
-In consideration of the work in progress of porting all Tails shell scripts to Python 3, and the good reasons for this, the Tails Server should also be implemented in Python 3.
+In consideration of the work in progress of porting all Tails shell scripts to Python 3, and the good reasons for this, Tails Server should also be implemented in Python 3.
# Service Specification #