mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

enable-tor: When run as a regular user, test a connection back to the hidden service over tor.

Browse source 
This way we know that after enable-tor, the tor hidden service is fully
published and working, and so there should be no problems with it at
pairing time.

It has to start up its own temporary listener on the hidden service. It
would be nice to have it start the remotedaemon running, so that extra
step is not needed afterwards. But, there may already be a remotedaemon
running, in communication with the assistant and we don't want to start
another one. I thought about trying to HUP any running remotedaemon, but
Windows does not make it easy to do that. In any case, having the user
start the remotedaemon themselves lets them know it needs to be running
to serve the hidden service.

This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
This commit is contained in:
Joey Hess 2016-12-24 12:49:28 -04:00
parent f3a4b9191c
commit e08691b393
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
5 changed files with 78 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

3
doc/tips/peer_to_peer_network_with_tor.mdwn
View file

@ -26,7 +26,8 @@ In each git-annex repository, run these commands:
git annex enable-tor
git annex remotedaemon
Now git-annex is running as a Tor hidden service, but
The enable-tor command may prompt for the root password, since it
configures Tor. Now git-annex is running as a Tor hidden service, but
it will only talk to peers after pairing with them.
In both repositories, run this command: