[tor-bugs] #18329 [Core Tor/Tor]: Let bridges indicate when they don't want BridgeDB to distribute their address

Tor Bug Tracker & Wiki blackhole at torproject.org
Mon May 15 22:51:58 UTC 2017


#18329: Let bridges indicate when they don't want BridgeDB to distribute their
address
------------------------------+------------------------------------
 Reporter:  karsten           |          Owner:
     Type:  enhancement       |         Status:  needs_revision
 Priority:  Medium            |      Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor      |        Version:
 Severity:  Normal            |     Resolution:
 Keywords:  tor-bridge, stem  |  Actual Points:
Parent ID:                    |         Points:  .2 remaining
 Reviewer:  nickm             |        Sponsor:
------------------------------+------------------------------------
Changes (by dcf):

 * cc: catalyst (removed)


Comment:

 Replying to [comment:5 arma]:
 > My {{{feature18329}}} branch implements this feature.
 >
 > There's a new BridgeDistribution torrc option, and it passes along its
 argument into the new bridge-distribution-request line in the bridge
 descriptor.

 https://gitweb.torproject.org/arma/tor.git/commit/?h=feature18329&id=da46e73142bd522f8ac7dfc9d1f113c6281aea85

 Do we care about potentially having different distribution settings for
 the potentially multiple transports that may be defined in torrc? If
 someone has both `ServerTransportPlugin obfs3` and `ServerTransportPlugin
 obfs4`, say, there would be no way to give them different
 `BridgeDistribution` settings.

 Currently some torrc options are keyed on transport name (e.g.
 [https://www.torproject.org/docs/tor-manual.html.en#ServerTransportPlugin
 ServerTransportPlugin], [https://www.torproject.org/docs/tor-
 manual.html.en#ServerTransportListenAddr ServerTransportListenAddr],
 [https://www.torproject.org/docs/tor-manual.html.en#ServerTransportOptions
 ServerTransportOptions]). Ought `BridgeDistribution` to be like that too,
 or is it too niche a use case?

 By transport name would be the finest possible granularity. It would be
 cool if you could run multiple instances of obfs4 with different
 `BridgeDistribution` options, but you can't actually express multiple
 instances of the same transport name in torrc (see #11211). So if someone
 wanted to do that, they would have to run multiple instances of tor with
 multiple fingerprints anyway.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18329#comment:32>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list