#33582: Make bridges wait until they have bootstrapped, before publishing their
descriptor
-------------------------------------------------+-------------------------
Reporter: teor | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: Tor:
| 0.4.4.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-bridge, tor-relay, prop311, | Actual Points:
outreachy-ipv6, easy |
Parent ID: #33050 | Points: 1
Reviewer: | Sponsor:
| Sponsor55-can
-------------------------------------------------+-------------------------
Old description:
> On bridges, there's a race condition when bridges try to publish their
> descriptor to the bridge authority:
> * bridges try to publish their descriptors before bootstrapping
> * but bridges can't publish their descriptors, because they don't have
> enough directory info to build a circuit to the bridge authority
>
> Bridges will eventually try to publish their descriptors again, when they
> become dirty.
>
> We should make bridges wait until they have bootstrapped, before they try
> to publish their descriptors. (This might be a good change for relays as
> well: there isn't much point in publishing a relay that can't bootstrap.)
>
> This issue happens regardless of `AssumeReachable`. It is most obvious in
> chutney networks.
New description:
Instead of this fix, we can make chutney check tor's logs for reachability
self-test successes. See #34037.
On bridges, there's a race condition when bridges try to publish their
descriptor to the bridge authority:
* bridges try to publish their descriptors before bootstrapping
* but bridges can't publish their descriptors, because they don't have
enough directory info to build a circuit to the bridge authority
Bridges will eventually try to publish their descriptors again, when they
become dirty.
We should make bridges wait until they have bootstrapped, before they try
to publish their descriptors. (This might be a good change for relays as
well: there isn't much point in publishing a relay that can't bootstrap.)
This issue happens regardless of `AssumeReachable`. It is most obvious in
chutney networks.
--
Comment (by teor):
Instead of this fix, we can make chutney check tor's logs for reachability
self-test successes. See #34037.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33582#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
