Lay down some infrastructure for bridges in the New Guard Order.
commit1d52ac4d3f67a6e3fac3602f87d00c14060068ab
authorNick Mathewson <nickm@torproject.org>
Tue, 29 Nov 2016 13:04:41 +0000 (29 08:04 -0500)
committerNick Mathewson <nickm@torproject.org>
Fri, 16 Dec 2016 16:06:18 +0000 (16 11:06 -0500)
tree6c46116e71af72e049d0f278a85ea09567b6d3ac
parent89f5f149df984bab00de9868a9305b611c4aa17e
Lay down some infrastructure for bridges in the New Guard Order.

This includes:
  * making bridge_info_t exposed but opaque
  * allowing guards where we don't know an identity
  * making it possible to learn the identity of a guard
  * creating a guard that lacks a node_t
  * remembering a guard's address and port.
  * Looking up a guard by address and port.
  * Only enforcing the rule that we need a live consensus to update
    the "listed" status for guards when we are not using bridges.
src/common/address.c
src/common/address.h
src/or/bridges.c
src/or/bridges.h
src/or/entrynodes.c
src/or/entrynodes.h
src/test/test_entrynodes.c