diff options
author | 2016-12-24 12:49:28 -0400 | |
---|---|---|
committer | 2016-12-24 12:50:23 -0400 | |
commit | 3959f2ad9b17f91e6f42310b991c9e22d8f8f4e3 (patch) | |
tree | 3958f3ba6f2d439f96f33905d610b808ebaa6304 /doc/todo/tor.mdwn | |
parent | 856fa66695468e890749279e0b8ddfe60283f112 (diff) |
enable-tor: When run as a regular user, test a connection back to the hidden service over tor.
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.
Diffstat (limited to 'doc/todo/tor.mdwn')
-rw-r--r-- | doc/todo/tor.mdwn | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/todo/tor.mdwn b/doc/todo/tor.mdwn index f0c193677..cb0bc4d41 100644 --- a/doc/todo/tor.mdwn +++ b/doc/todo/tor.mdwn @@ -4,7 +4,6 @@ Mostly working! Current todo list: -* Make enable-tor check connection back to itself to verify tor is working. * When a transfer can't be done because another transfer of the same object is already in progress, the message about this is output by the remotedaemon --debug, but not forwarded to the peer, which shows |