From fc77c4c9006e2aa39672efe21fea28e47c331a6d Mon Sep 17 00:00:00 2001 From: akwizgran <michael@briarproject.org> Date: Thu, 14 Mar 2019 15:14:58 +0000 Subject: [PATCH] Update BTP.md --- protocols/BTP.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/protocols/BTP.md b/protocols/BTP.md index 31347cc..d6c17d6 100644 --- a/protocols/BTP.md +++ b/protocols/BTP.md @@ -14,7 +14,7 @@ The BTP wire protocol includes optional padding and does not use any timeouts, h BTP does not attempt to conceal the identities of the communicating parties or the fact that they are communicating - in other words, it does not provide anonymity, unlinkability or unobservability. If such properties are required, BTP can use an anonymity system such as Tor as the underlying transport. -Forward secrecy is achieved by establishing an initial root key between pair of endpoint devices and using a one-way key derivation function to derive a series of temporary keys from the root key. Once both endpoints have deleted a given key, it cannot be re-derived if the endpoints are later compromised. +Forward secrecy is achieved by establishing an initial root key between a pair of endpoint devices and using a one-way key derivation function to derive a series of temporary keys from the root key. Once both endpoints have deleted a given key, it cannot be re-derived if the endpoints are later compromised. ### 1.1 Motivation @@ -94,7 +94,7 @@ Before two endpoints can communicate using BTP they must agree on the following - **Maximum latency** - The endpoints must agree on the maximum expected latency, **L**, of each transport they wish to use. This value may be hard-coded. For any given transport we can choose some maximum latency L such that the latency of any connection is unlikely to exceed L under normal conditions. For example, we might choose one minute as the maximum latency for TCP, or two weeks as the maximum latency for disks sent through the mail. If a connection exceeds the maximum latency, none of BTP's security properties are lost but it may reject the stream or streams carried by the connection. + The endpoints must agree on the maximum expected latency, **L**, of each transport they wish to use. This value may be hard-coded. For any given transport we can choose some maximum latency that is unlikely to be exceeded under normal conditions. For example, we might choose one minute as the maximum latency for TCP, or two weeks as the maximum latency for disks sent through the mail. If a connection exceeds the maximum latency, none of BTP's security properties are lost but it may reject the stream or streams carried by the connection. ### 1.6 Notation -- GitLab