Skip to content
Snippets Groups Projects
Select Git revision
  • improved-logging
  • main default protected
  • fix-163
  • ping-increase
  • update
  • fmt
  • debian-worker
  • reqwest
  • xz
  • base64
  • fedora
  • release
  • chunked-gc
  • make-install
  • clippy
  • bump
  • bump-deps
  • tails-key
  • misc
  • fix-tails
  • post-body-size-limit
  • v0.24.0
  • v0.23.1
  • v0.23.0
  • v0.22.1
  • v0.22.0
  • v0.21.0
  • v0.20.0
  • v0.19.0
  • v0.18.1
  • v0.18.0
  • v0.17.0
  • v0.16.6
  • v0.16.5
  • v0.16.4
  • v0.16.3
  • v0.16.2
  • v0.16.1
  • v0.16.0
  • v0.15.0
  • v0.14.2
41 results

rebuilder-tails.sh

Blame
  • README.md NaN GiB
    # control
    
    A simple control plane for the obfsvpn node.
    It's part of the [obfsvpn-server](/images/obfsvpn/Dockerfile) docker image.
    
    Control is intended to be used for communication between different services, such as the gateway and bridge distribution service  [Menshen](https://0xacab.org/leap/menshen).
    
    It exposes the bridge configuration and offers to flag a node as down for maintenance.
    
    The endpoints listening to GET requests are:
    * `/bridge`: returns bridge config as IP, port, certificate, location and maintenance state
    * `/enable`: flags the bridge as working
    * `/disable`: flags the bridge as being in maintenance
    
    A couple of environment variables need to be set to run control:
    
    `CONTROL_PORT`: port control is listening to
    `OBFSVPN_STATE`: directory of private and public key, certifcate, bridge-line file
    `OBFSVPN_LOCATION`: key representing a location of the OpenVPN gateway the bridge is pointing to. It will be used by [Menshen](https://0xacab.org/leap/menshen) to filter requests to the Menshen API for a bridge location 
    `OBFS4_IP`: public IP of the bridge, exposed in the Menshen API
    `OBFS4_PORT`: port of the bridge, exposed in the Menshen API