tordam

A library for peer discovery inside the Tor network
git clone https://git.parazyd.org/tordam
Log | Files | Refs | README | LICENSE

commit 1bcaf450d010e5b8356d06116abeb7e9789c4ff0
parent b2c4cc3445dc9e3105dc240031a8c2c060e9cf70
Author: parazyd <parazyd@dyne.org>
Date:   Tue, 13 Feb 2018 23:40:31 +0100

Fix wording in protocol.md

Reported by tg.

Diffstat:
Mprotocol.md | 4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/protocol.md b/protocol.md @@ -15,7 +15,7 @@ Abstract * A node announces itself to directories by sending a JSON-formatted HTTP POST request to one or more active nodes/directories. * Once the POST request is received, the directory will validate the - request and return a secret encrypted with the requester's private + request and return a secret encrypted with the requester's public key. * The requester will try to decrypt this secret, and return it plain back to the directory, along with a cryptographic signature, so the @@ -61,7 +61,7 @@ signature that was made. Validating this, we assume that the requester is in possession of the private key. Following up, the directory will generate a cryptographically secure -random string and encrypt it using the before acquired private key. It +random string and encrypt it using the before acquired public key. It will then be encoded using base64 and sent back to the client: