[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #27402 [Core Tor/Tor]: stop reporting "internal paths" during bootstrap
#27402: stop reporting "internal paths" during bootstrap
-------------------------------------------------+-------------------------
Reporter: catalyst | Owner: teor
Type: enhancement | Status:
| assigned
Priority: Medium | Milestone: Tor:
| 0.3.5.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: s8-bootstrap, tor-spec, | Actual Points:
034-backport, 034-must |
Parent ID: | Points:
Reviewer: | Sponsor:
| Sponsor8-can
-------------------------------------------------+-------------------------
Comment (by catalyst):
Replying to [comment:1 teor]:
> This issue is caused (or made much worse) by #27236, which makes the
chutney bridge and onion service networks work again after changes in
0.3.4.
>
> If we remove the relevant code, then most of the chutney networks will
stop working.
>
> Instead, let's fix the log message so it correctly reports that:
> * there are exits in the consensus, but they don't have descriptors, or
> * there are no exits in the consensus
I'm not sure I understand. Does chutney require that the bootstrap log
messages distinguish between having exits and not having exits? Is there
some place other than the bootstrap status messages where it makes sense
to report this information?
I think it might make sense to report this somewhere else. In practice,
barring catastrophe, don't we expect the live Tor network to always have
exits? Maybe the distinction is only important for test networks.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27402#comment:2>
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