From 04ec673d517240ec88f18710d43cf0325e6dc546 Mon Sep 17 00:00:00 2001 From: "branchable@bafd175a4b99afd6ed72501042e364ebd3e0c45e" Date: Sun, 29 Sep 2019 23:34:25 +0000 Subject: [PATCH] Fix typo and incorrect references to "git annex peer" --- doc/tips/peer_to_peer_network_with_tor.mdwn | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/tips/peer_to_peer_network_with_tor.mdwn b/doc/tips/peer_to_peer_network_with_tor.mdwn index 8e06931d86..2a9287a5a8 100644 --- a/doc/tips/peer_to_peer_network_with_tor.mdwn +++ b/doc/tips/peer_to_peer_network_with_tor.mdwn @@ -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/`