5 Commits

Author	SHA1	Message	Date
Nick Mathewson	1582adabbb	Change approach to preventing duplicate guards. ... Previously I'd made a bad assumption in the implementation of prop271 in 0.3.0.1-alpha: I'd assumed that there couldn't be two guards with the same identity. That's true for non-bridges, but in the bridge case, we allow two bridges to have the same ID if they have different addr:port combinations -- in order to have the same bridge ID running multiple PTs. Fortunately, this assumption wasn't deeply ingrained: we stop enforcing the "one guard per ID" rule in the bridge case, and instead enforce "one guard per <id,addr,port>". We also needed to tweak our implementation of get_bridge_info_for_guard, since it made the same incorrect assumption. Fixes bug 21027; bugfix on 0.3.0.1-alpha.	2017-02-28 08:16:33 -05:00
Nick Mathewson	2cee38f76a	Merge branch 'prop271_030_v1_squashed'	2016-12-16 11:20:59 -05:00
Nick Mathewson	53f248f6c9	Add some needed accessors/inspectors for bridge/guard convergence	2016-12-16 11:06:18 -05:00
Nick Mathewson	1d52ac4d3f	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.	2016-12-16 11:06:18 -05:00
Nick Mathewson	8da24c99bd	Split bridge functions into a new module. ... This patch is just: * Code movement * Adding headers here and there as needed * Adding a bridges_free_all() with a call to it. It breaks compilation, since the bridge code needed to make exactly 2 calls into entrynodes.c internals. I'll fix those in the next commit.	2016-11-30 14:42:52 -05:00