[tor-bugs] #21864 [Core Tor/Tor]: Support Bridges setting MyFamily to include Relays

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#21864: Support Bridges setting MyFamily to include Relays
------------------------------+-------------------------
     Reporter:  isis          |      Owner:
         Type:  defect        |     Status:  new
     Priority:  Medium        |  Milestone:
    Component:  Core Tor/Tor  |    Version:
     Severity:  Normal        |   Keywords:  easy, 15min
Actual Points:                |  Parent ID:
       Points:  0.5           |   Reviewer:
      Sponsor:                |
------------------------------+-------------------------
 In src/or/config.c:
 {{{
   if (options->MyFamily && options->BridgeRelay) {
     log_warn(LD_CONFIG, "Listing a family for a bridge relay is not "
              "supported: it can reveal bridge fingerprints to censors. "
              "You should also make sure you aren't listing this bridge's "
              "fingerprint in any other MyFamily.");
   }
 }}}

 In src/or/router.c, function `router_build_fresh_descriptor`:
 {{{
   if (options->MyFamily && ! options->BridgeRelay) {
     smartlist_t *family;
   […]
 }}}

 I propose instead that we:

 1) Warn bridge operators not to include ''other'' bridges in MyFamily, but
 let them know that including relays is fine. We should continue to warn
 them not to list any bridge in the MyFamily of a public relay.
 2) Allow bridges to specify MyFamily.

 The reasoning for this is that NoiseTor would like to run high-capacity
 default bridges for Tor Browser, but they are nervous about simultaneously
 running exits without being able to direct people not to use both.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21864>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs