Skip to content
Snippets Groups Projects
Commit 738a5a12 authored by Thomas's avatar Thomas Committed by akwizgran
Browse files

Clarify BRP Attack Vector

parent fcff6feb
No related branches found
No related tags found
1 merge request!4Clarify BRP Attack Vector
......@@ -22,7 +22,7 @@ Before they can connect, the peers need to know how to contact each other. A str
We assume the adversary can read, modify, delete and insert traffic on all transports at will.
We do not assume that the peers exchanged their public keys over a secure channel. If the adversary intercepted the prior exchange of public keys and replaced them with its own public keys then BRP does not detect or prevent man-in-the-middle attacks.
Practically we should not assume that the peers exchanged their public keys over a secure channel. If the adversary intercepted the prior exchange of public keys and replaced them with its own public keys then BRP can not detect or prevent man-in-the-middle attacks. (Limitation)
If the adversary knows both peers' public keys but did not replace them during the prior exchange then BRP prevents the adversary from learning the peers' network addresses, unless the adversary can see the addresses by observing the underlying transport.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment