Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time
44 lines (25 sloc) 3.62 KB

Tor integration

WARNING: Tor integration in Gridsync is currently experimental and is being made available for testing purposes only. As such -- and so long as this notice remains -- it should be considered both potentially unsafe and/or subject to change; do not rely upon this (yet)!


Beginning in version 0.4, Gridsync provides built-in support for tunneling outgoing connections over the Tor anonymity network. This allows users to connect to storage grids and share folders without revealing their geographical location to any of the parties typically involved in such activities, including:

  • The operator of the storage grid and any/all introducer/storage nodes
  • The magic-wormhole server used to negotiate grid and folder invites
  • Any servers specified in the icon_url field of incoming invite messages


Currently, Gridsync will only offer the option to connect via Tor on systems where a tor daemon is already running and a usable "control port" is exposed; upon startup, Gridsync will search for an accessible control port at the following locations:

  • /var/run/tor/control (UNIX socket): The default on Debian-based GNU/Linux systems
  • localhost:9051 (TCP): The standard control port for standalone tor daemons
  • localhost:9151 (TCP): The standard control port for TorBrowser's embedded tor daemon

If Gridsync cannot find a running Tor daemon via any one of the above locations, the option to create new connections over the Tor network will be unavailable, while any existing grid connections previously-configured to use Tor will fail (with an error-message) until a new/working tor daemon is launched. Gridsync will not attempt to connect without Tor for any connection that has Tor enabled.

(Note: In the future, Gridsync may offer the option to launch/configure a Tor daemon automatically on startup or when needed; see Issue #??)


If Gridsync finds a running tor daemon at any one of the above-mentioned locations, a "Connect over the Tor network" checkbox will become available beneath invite code entry-fields (as found, e.g., on the initial/first-run "welcome" screen when adding a new grid or folder from an invite code). Switching this checkbox "on" before proceeding will force any subsequent connections associated with that invitation/connection to be tunneled through the Tor network, in particular: 1) connecting to the magic-wormhole server, 2) fetching any service icons, and 3) the resulting Tahoe-LAFS connection(s) to the storage grid.

Alternatively, users may choose to enable Tor for new connections from the manual configuration dialog (i.e., by selecting "Tor" from the "Connections" combobox/dropdown menu).

(Note: To help protect against accidental deanonymization, Gridsync does not provide the option to disable Tor connections once enabled; users wishing to connect to an existing Tor-enabled grid without Tor should create a new connection to that grid with Tor disabled; see Issue #100)

Other notes

Gridsync's Tor integration relies largely upon -- and makes use of -- the existing implementations for Tor support already present in the Magic-Wormhole and Tahoe-LAFS applications. See the relevant documentation for each implementation (here and here, respectively) for further details.