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
..
.dummy	Add a .dummy file in the changes directory to stop git from removing it	2015-05-11 11:41:48 -04:00
bug21027	Change approach to preventing duplicate guards.	2017-02-28 08:16:33 -05:00
bug21116	test: Add missing socket errno in test_util.c	2017-02-08 09:00:48 -05:00
geoip-february2017	Update geoip and geoip6 to the February 8 2017 database.	2017-02-12 15:56:31 +01:00