From 87896a7d79ecfe06d2538e719061d6e75e1d7952 Mon Sep 17 00:00:00 2001 From: Micah Anderson Date: Tue, 21 Nov 2017 10:05:14 -0500 Subject: Docs: Update docs to prepare for 0.10.0 release Fixes: #8427, #8812 --- docs/en/services/couchdb.html | 2 +- docs/en/services/couchdb/index.html | 2 +- docs/en/services/index.html | 2 +- docs/en/services/mx.html | 4 ++-- docs/en/services/mx/index.html | 4 ++-- docs/en/services/openvpn.html | 2 +- docs/en/services/openvpn/index.html | 2 +- docs/en/services/tor.html | 48 ++++++++++++++++++++++++++----------- docs/en/services/tor/index.html | 48 ++++++++++++++++++++++++++----------- 9 files changed, 77 insertions(+), 37 deletions(-) (limited to 'docs/en/services') diff --git a/docs/en/services/couchdb.html b/docs/en/services/couchdb.html index de50a692..43f7cfac 100644 --- a/docs/en/services/couchdb.html +++ b/docs/en/services/couchdb.html @@ -215,7 +215,7 @@ couchdb - LEAP Platform Documentation diff --git a/docs/en/services/couchdb/index.html b/docs/en/services/couchdb/index.html index 9eb7fcb8..b48c4eb7 100644 --- a/docs/en/services/couchdb/index.html +++ b/docs/en/services/couchdb/index.html @@ -215,7 +215,7 @@ couchdb - LEAP Platform Documentation diff --git a/docs/en/services/index.html b/docs/en/services/index.html index 6d5c68e1..261cd11b 100644 --- a/docs/en/services/index.html +++ b/docs/en/services/index.html @@ -235,7 +235,7 @@ Services - LEAP Platform Documentation

tor

-
Tor exit node or hidden service
+
Tor services: relay, exit node and hidden service

diff --git a/docs/en/services/mx.html b/docs/en/services/mx.html index 8f5a36da..aa41186a 100644 --- a/docs/en/services/mx.html +++ b/docs/en/services/mx.html @@ -156,8 +156,8 @@ mx - LEAP Platform Documentation
  1. alias lists: by specifying an array of destination addresses, as in the case of “flock”, the single email will get copied to each address.
    2. -
  2. chained resolution: alias resolution will recursively continue until there are no more matching aliases. For example, “flock” is resolved to “robin”, which then gets resolved to “robin@bird.org”.
    3. -
  3. virtual domains: by specifying the full domain, as in the case of “chickadee@avian.org”, the alias will work for any domain you want. Of course, the MX record for that domain must point to appropriate MX servers, but otherwise you don’t need to do any additional configuration.
    4. +
  4. chained resolution: alias resolution will recursively continue until there are no more matching aliases. For example, “flock” is resolved to “robin”, which then gets resolved to “robin@bird.org”.
    5. +
  5. virtual domains: by specifying the full domain, as in the case of “chickadee@avian.org”, the alias will work for any domain you want. Of course, the MX record for that domain must point to appropriate MX servers, but otherwise you don’t need to do any additional configuration.
  6. local delivery: for testing purposes, it is often useful to copy all incoming mail for a particular address and send those copies to another address. You can do this by adding “@deliver.local” as one of the destination addresses. When “@local.delivery” is found, alias resolution stops and the mail is delivered to that username.
diff --git a/docs/en/services/mx/index.html b/docs/en/services/mx/index.html index e8e06e80..048f5198 100644 --- a/docs/en/services/mx/index.html +++ b/docs/en/services/mx/index.html @@ -156,8 +156,8 @@ mx - LEAP Platform Documentation
  1. alias lists: by specifying an array of destination addresses, as in the case of “flock”, the single email will get copied to each address.
    2. -
  2. chained resolution: alias resolution will recursively continue until there are no more matching aliases. For example, “flock” is resolved to “robin”, which then gets resolved to “robin@bird.org”.
    3. -
  3. virtual domains: by specifying the full domain, as in the case of “chickadee@avian.org”, the alias will work for any domain you want. Of course, the MX record for that domain must point to appropriate MX servers, but otherwise you don’t need to do any additional configuration.
    4. +
  4. chained resolution: alias resolution will recursively continue until there are no more matching aliases. For example, “flock” is resolved to “robin”, which then gets resolved to “robin@bird.org”.
    5. +
  5. virtual domains: by specifying the full domain, as in the case of “chickadee@avian.org”, the alias will work for any domain you want. Of course, the MX record for that domain must point to appropriate MX servers, but otherwise you don’t need to do any additional configuration.
  6. local delivery: for testing purposes, it is often useful to copy all incoming mail for a particular address and send those copies to another address. You can do this by adding “@deliver.local” as one of the destination addresses. When “@local.delivery” is found, alias resolution stops and the mail is delivered to that username.
diff --git a/docs/en/services/openvpn.html b/docs/en/services/openvpn.html index e5fe1128..1a420e21 100644 --- a/docs/en/services/openvpn.html +++ b/docs/en/services/openvpn.html @@ -133,8 +133,8 @@ openvpn - LEAP Platform Documentation

Essential configuration

    -
  • openvpn.gateway_address: The address that OpenVPN daemon is bound to and that VPN clients connect to.
  • ip_address: The main IP of the server, and the egress address for outgoing traffic.
    • +
  • openvpn.gateway_address: A secondary address on the same machine (sharing the same interface, or on a separate interface). The OpenVPN daemon is bound to this address and VPN clients connect to it.
diff --git a/docs/en/services/openvpn/index.html b/docs/en/services/openvpn/index.html index 4a9dc993..23866436 100644 --- a/docs/en/services/openvpn/index.html +++ b/docs/en/services/openvpn/index.html @@ -133,8 +133,8 @@ openvpn - LEAP Platform Documentation

Essential configuration

    -
  • openvpn.gateway_address: The address that OpenVPN daemon is bound to and that VPN clients connect to.
  • ip_address: The main IP of the server, and the egress address for outgoing traffic.
    • +
  • openvpn.gateway_address: A secondary address on the same machine (sharing the same interface, or on a separate interface). The OpenVPN daemon is bound to this address and VPN clients connect to it.
diff --git a/docs/en/services/tor.html b/docs/en/services/tor.html index f649c086..1f6ce112 100644 --- a/docs/en/services/tor.html +++ b/docs/en/services/tor.html @@ -110,7 +110,7 @@ tor - LEAP Platform Documentation

tor

-
Tor exit node or hidden service
+
Tor services: relay, exit node and hidden service
    @@ -124,33 +124,53 @@ tor - LEAP Platform Documentation

    Topology

    -

    Nodes with tor service will run a Tor exit or hidden service, depending on what other service it is paired with:

    +

    Nodes with tor service will run a Tor relay with some pre-defined settings, which can be changed with some configuration (see Configuration below). You can enable an exit or a hidden service with additional configuration.

    + +

    Configuration

    + +

    By default, if a node has service ‘tor’ configured, it will run a tor relay (not an exit). The relay will be configured with bandwidth limitations, contacts, a nickname and a family. The defaults for these (shown below), can be overridden as desired.

      -
    • tor + openvpn: when combined with openvpn nodes, tor will create a Tor exit node to provide extra cover traffic for the VPN. This can be especially useful if there are VPN gateways without much traffic.
      • -
    • tor + webapp: when combined with a webapp node, the tor service will make the webapp and the API available via .onion hidden service.
      • -
    • tor stand alone: a regular Tor exit node.
      • +
    • tor.bandwidth_rate: the max bandwidth allocated to Tor, in KB per second, when used as an exit node (default: 6550 KB/sec).
      • +
    • tor.type: what type of tor node to make, at this moment only ‘exit’ is supported. If not specified, acts as a relay.
      • +
    • tor.contacts: the contact information for the relay (default: the list of provider contacts)
      • +
    • tor.nickname: the nickname of the relay (default: a combination of the node name and a hash of the family)
      • +
    • tor.family: a list of the other nicknames that are part of the same provider
      • +
    • tor.hidden_service: to enable a hidden service, set ‘active’ to be true (see below for an example), do not configure “services”: [“tor”] for the node!
    -

    If activated, you can list the hidden service .onion addresses this way:

    +

    Examples:

    -

    leap ls –print tor.hidden_service.address tor

    +

    To add a relay to a node:

    -

    Then just add ‘.onion’ to the end of the printed addresses.

    +
    { 
+ "services": ["tor"]
+}
+
    -

    Configuration

    +

    To enable a hidden service, without a relay, do not specify the tor service (it is not considered secure to have a node configured as a relay and a hidden service at the same time, see: https://trac.torproject.org/8742), instead configure the node to have the following:

    -
      -
    • tor.bandwidth_rate: the max bandwidth allocated to Tor, in KB per second, when used as an exit node.
      • -
    +
    {
+  "tor": {
+    "hidden_service": {
+    "active": true
+  }
+}
+
    +

    If activated, you can list the hidden service .onion addresses this way:

    + +

    leap ls –print tor.hidden_service.address tor

    + +

    Then just add ‘.onion’ to the end of the printed addresses.

    -

    For example:

    +

    To enable a Tor exit node:

    {
   "tor": {
-    "bandwidth_rate": 6550
+    "bandwidth_rate": 6550,
+    "type": "exit"
   }
 }
    diff --git a/docs/en/services/tor/index.html b/docs/en/services/tor/index.html index 8fecf152..a6380d90 100644 --- a/docs/en/services/tor/index.html +++ b/docs/en/services/tor/index.html @@ -110,7 +110,7 @@ tor - LEAP Platform Documentation

    tor

    -
    Tor exit node or hidden service
    +
    Tor services: relay, exit node and hidden service
      @@ -124,33 +124,53 @@ tor - LEAP Platform Documentation

      Topology

      -

      Nodes with tor service will run a Tor exit or hidden service, depending on what other service it is paired with:

      +

      Nodes with tor service will run a Tor relay with some pre-defined settings, which can be changed with some configuration (see Configuration below). You can enable an exit or a hidden service with additional configuration.

      + +

      Configuration

      + +

      By default, if a node has service ‘tor’ configured, it will run a tor relay (not an exit). The relay will be configured with bandwidth limitations, contacts, a nickname and a family. The defaults for these (shown below), can be overridden as desired.

        -
      • tor + openvpn: when combined with openvpn nodes, tor will create a Tor exit node to provide extra cover traffic for the VPN. This can be especially useful if there are VPN gateways without much traffic.
        • -
      • tor + webapp: when combined with a webapp node, the tor service will make the webapp and the API available via .onion hidden service.
        • -
      • tor stand alone: a regular Tor exit node.
        • +
      • tor.bandwidth_rate: the max bandwidth allocated to Tor, in KB per second, when used as an exit node (default: 6550 KB/sec).
        • +
      • tor.type: what type of tor node to make, at this moment only ‘exit’ is supported. If not specified, acts as a relay.
        • +
      • tor.contacts: the contact information for the relay (default: the list of provider contacts)
        • +
      • tor.nickname: the nickname of the relay (default: a combination of the node name and a hash of the family)
        • +
      • tor.family: a list of the other nicknames that are part of the same provider
        • +
      • tor.hidden_service: to enable a hidden service, set ‘active’ to be true (see below for an example), do not configure “services”: [“tor”] for the node!
      -

      If activated, you can list the hidden service .onion addresses this way:

      +

      Examples:

      -

      leap ls –print tor.hidden_service.address tor

      +

      To add a relay to a node:

      -

      Then just add ‘.onion’ to the end of the printed addresses.

      +
      { 
+ "services": ["tor"]
+}
+
      -

      Configuration

      +

      To enable a hidden service, without a relay, do not specify the tor service (it is not considered secure to have a node configured as a relay and a hidden service at the same time, see: https://trac.torproject.org/8742), instead configure the node to have the following:

      -
        -
      • tor.bandwidth_rate: the max bandwidth allocated to Tor, in KB per second, when used as an exit node.
        • -
      +
      {
+  "tor": {
+    "hidden_service": {
+    "active": true
+  }
+}
+
      +

      If activated, you can list the hidden service .onion addresses this way:

      + +

      leap ls –print tor.hidden_service.address tor

      + +

      Then just add ‘.onion’ to the end of the printed addresses.

      -

      For example:

      +

      To enable a Tor exit node:

      {
   "tor": {
-    "bandwidth_rate": 6550
+    "bandwidth_rate": 6550,
+    "type": "exit"
   }
 }
      -- cgit v1.2.3