From 78e9d62c655f4ad8336d394a3071e38e0c5fb4a2 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 7 Jul 2025 13:22:08 -0400 Subject: [PATCH] correction --- .../comment_2_57e4608559b0873617c82d5454cab798._comment | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/todo/generic_p2p_socket_transport/comment_2_57e4608559b0873617c82d5454cab798._comment b/doc/todo/generic_p2p_socket_transport/comment_2_57e4608559b0873617c82d5454cab798._comment index 2780e6b75b..9367e9e323 100644 --- a/doc/todo/generic_p2p_socket_transport/comment_2_57e4608559b0873617c82d5454cab798._comment +++ b/doc/todo/generic_p2p_socket_transport/comment_2_57e4608559b0873617c82d5454cab798._comment @@ -20,8 +20,9 @@ the generic one could be "p2p-annex::". Or it could be `git-annex-p2p-foo ` and talk to its stdin and stdout. That's for outgoing connections. For incoming connections, -for tor, the remotedaemon looks to see if the socket file exists and -if so it accepts connections from it. (That tor socket is not used for +for tor, the remotedaemon creates the socket file that tor is configured to +use for the hidden service, and listens to it +to accept connections from tor. (That tor socket is not used for outgoing connections.) It would be easy to generalize this to additional socket filenames. Eg, a remote with uuid U could use `.git/annex/p2p/U` as its socket file.