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

Fix typo and incorrect references to "git annex peer"

Browse source
This commit is contained in:
branchable@bafd175a4b99afd6ed72501042e364ebd3e0c45e 2019-09-29 23:34:25 +00:00 committed by admin
parent 3f609a7742
commit 04ec673d51
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/tips/peer_to_peer_network_with_tor.mdwn
View file

@ -171,8 +171,8 @@ how it works.
git-annex's Tor support uses onion address as the address of a git remote.
You can `git pull`, push, etc with those onion addresses:
git pull tor-annnex::eeaytkuhaupbarfi.onion:4412
git remote add peer1 tor-annnex::eeaytkuhaupbarfi.onion:4412
git pull tor-annex::eeaytkuhaupbarfi.onion:4412
git remote add peer1 tor-annex::eeaytkuhaupbarfi.onion:4412
Onion addresses are semi-public. When you add a remote, they appear in your
`.git/config` file. For security, there's a second level of authentication
@ -180,10 +180,10 @@ that git-annex uses to make sure that only people you want to can access
your repository over Tor. That takes the form of a long string of numbers
and letters, like "7f53c5b65b8957ef626fd461ceaae8056e3dbc459ae715e4".
The addresses generated by `git annex peer --gen-addresses`
The addresses generated by `git annex p2p --gen-addresses`
combine the onion address with the authentication data.
When you run `git annex peer --link`, it sets up a git remote using
When you run `git annex p2p --link`, it sets up a git remote using
the onion address, and it stashes the authentication data away in a file in
`.git/annex/creds/`