Opened 13 months ago

Last modified 6 weeks ago

#21573 new defect

Fix tor warnings that chutney is currently ignoring

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.3.4.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points: 3
Reviewer: Sponsor:


Chutney ignores a large number of common tor warnings in order to produce readable output from its script:

Some of these warnings have individual tickets (I'll parent them to this task).

Of the remainder, we can probably remove the tor warnings for:

  • expands into rules which apply to all private IPv4 and IPv6 addresses

If we fixed consensus failures in chutney networks, we'd eliminate most of the rest, but there's a tradeoff here with bootstrap speed.

Some of the rest might be able to be fixed using chutney config changes.

And others are ok:
Some are expected every time tor is freshly launched.
Others are expected every time tor is running in a test network.

Child Tickets

#21524newprivate:* contains valid IPv6 addressesCore Tor/Tor
#21525newBootstrapping authorities sometimes expect a vote valid-after time of 0Core Tor/Tor
#21534closeddgoulet"Client asked me to extend back to the previous hop" in small networksCore Tor/Tor

Change History (2)

comment:1 Changed 6 months ago by nickm

Milestone: Tor: 0.3.2.x-finalTor: 0.3.3.x-final

comment:2 Changed 6 weeks ago by nickm

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

Defer a small handful of non-enhancement "new" tickets to 0.3.4

Note: See TracTickets for help on using tickets.