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

correction

Browse source
This commit is contained in:
Joey Hess 2025-07-07 13:22:08 -04:00
parent 0a89dc0d5d
commit 78e9d62c65
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
doc/todo/generic_p2p_socket_transport/comment_2_57e4608559b0873617c82d5454cab798._comment
View file

@ -20,8 +20,9 @@ the generic one could be "p2p-annex::<path-to-socket-file>". Or it could be
`git-annex-p2p-foo <bar>` 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.