tor/src
Nick Mathewson 7daf152172 Enforce Ed25519 identities (client-side)
This patch makes two absolutely critical changes:
  - If an ed25519 identity is not as expected when creating a channel,
    we call that channel unsuccessful and close it.
  - When a client creating a channel or an extend cell for a circuit, we
    only include the ed25519 identity if we believe that the node on
    the other side supports ed25519 link authentication (from
    #15055).  Otherwise we will insist on nodes without the right
    link protocol authenticating themselves.
  - When deciding to extend to another relay, we only upgrade the
    extend to extend by ed25519 ID when we know the ed25519 ID _and_
    we know that the other side can authenticate.

This patch also tells directory servers, when probing nodes, to
try to check their ed25519 identities too (if they can authenticate
by ed25519 identity).

Also, handle the case where we connect by RSA Id, and learn the
ED25519 ID for the node in doing so.
2016-12-08 16:47:58 -05:00
..
common Helper function for logging ed25519 public keys. 2016-12-08 16:47:58 -05:00
config In torrc.sample.in, note that bandwidth must be >=75 KB. 2016-11-08 19:23:49 -05:00
ext Regenerate trunnel code with trunnel 1.5 2016-10-26 11:06:45 -04:00
or Enforce Ed25519 identities (client-side) 2016-12-08 16:47:58 -05:00
test Rename connection_or_remove_from_identity_map 2016-12-08 16:47:57 -05:00
tools Merge branch 'maint-0.2.8' into maint-0.2.9 2016-11-03 15:41:04 -04:00
trunnel Trunnel-side: start migrating extend/extend2 to trunnel 2016-11-10 09:43:27 -05:00
win32 Bump version to 0.2.9.5-alpha-dev 2016-11-08 07:55:15 -05:00
include.am