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

1 files changed, 1 insertions, 2 deletions

diff --git a/doc/spec/dir-spec.txt b/doc/spec/dir-spec.txt
index bf9c1e690f..229eb891ad 100644
--- a/doc/spec/dir-spec.txt
+++ b/doc/spec/dir-spec.txt
@@ -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