Loading spec/rend-spec/encrypting-user-data.md +7 −0 Original line number Diff line number Diff line Loading @@ -10,3 +10,10 @@ Tor relay encryption protocol, applying encryption with these keys before other encryption, and decrypting with these keys before other decryption. The client encrypts with Kf and decrypts with Kb; the service host does the opposite. As mentioned [previously](./introduction-protocol.md#INTRO-HANDSHAKE-REQS), these keys are used the same as for [regular relay cell encryption](../tor-spec/routing-relay-cells.md), except that instead of using AES-128 and SHA1, both parties use AES-256 and SHA3-256. spec/rend-spec/introduction-protocol.md +3 −1 Original line number Diff line number Diff line Loading @@ -696,7 +696,9 @@ HANDSHAKE_INFO element (see \[JOIN_REND\]). The hidden service host now also knows the keys generated by the handshake, which it will use to encrypt and authenticate data end-to-end between the client and the server. These keys are as computed in tor-spec.txt section 5.1.4, except that instead of using computed with the [ntor handshake](../tor-spec/create-created-cells.html#ntor), except that instead of using AES-128 and SHA1 for this hop, we use AES-256 and SHA3-256. <a id="rend-spec-v3.txt-3.4"></a> Loading Loading
spec/rend-spec/encrypting-user-data.md +7 −0 Original line number Diff line number Diff line Loading @@ -10,3 +10,10 @@ Tor relay encryption protocol, applying encryption with these keys before other encryption, and decrypting with these keys before other decryption. The client encrypts with Kf and decrypts with Kb; the service host does the opposite. As mentioned [previously](./introduction-protocol.md#INTRO-HANDSHAKE-REQS), these keys are used the same as for [regular relay cell encryption](../tor-spec/routing-relay-cells.md), except that instead of using AES-128 and SHA1, both parties use AES-256 and SHA3-256.
spec/rend-spec/introduction-protocol.md +3 −1 Original line number Diff line number Diff line Loading @@ -696,7 +696,9 @@ HANDSHAKE_INFO element (see \[JOIN_REND\]). The hidden service host now also knows the keys generated by the handshake, which it will use to encrypt and authenticate data end-to-end between the client and the server. These keys are as computed in tor-spec.txt section 5.1.4, except that instead of using computed with the [ntor handshake](../tor-spec/create-created-cells.html#ntor), except that instead of using AES-128 and SHA1 for this hop, we use AES-256 and SHA3-256. <a id="rend-spec-v3.txt-3.4"></a> Loading