mirror of
https://github.com/torproject/torspec.git
synced 2025-03-02 22:06:10 +00:00
More work towards making bridge users able to connect via bridges:
- demand options->Bridges and options->TunnelDirConns if options->UseBridges is set. - after directory fetches, accept descriptors that aren't referenced by our networkstatuses, *if* they're for a configured bridge. - delay directory fetching until we have at least one bridge descriptor. - learn how to build a one-hop circuit when we have neither routerinfo nor routerstatus for our destination. - teach directory connections how to pick a bridge as the destination directory when doing non-anonymous fetches. - tolerate directory commands for which the dir_port is 0. - remember descriptors when the requested_resource was "authority", rather than just ignoring them. - put bridges on our entry_guards list once we have a descriptor for them. When UseBridges is set, only pick entry guards that are bridges. Else vice versa. svn:r10571
This commit is contained in:
parent
bfe73e803d
commit
d869b4cd6e
@ -192,14 +192,13 @@ $Id$
|
||||
corresponding roughly to "status votes" above. They would compute the
|
||||
result of the vote on the client side.
|
||||
|
||||
Authorities used sign documents using the same private keys they used
|
||||
Authorities used to sign documents using the same private keys they used
|
||||
for their roles as routers. This forced them to keep these extremely
|
||||
sensitive keys in memory unencrypted.
|
||||
|
||||
All of the information in extra-info documents used to be kept in the
|
||||
main descriptors.
|
||||
|
||||
|
||||
1.2. Document meta-format
|
||||
|
||||
Router descriptors, directories, and running-routers documents all obey the
|
||||
|
Loading…
x
Reference in New Issue
Block a user