Opened 4 years ago

Closed 2 years ago

#17090 closed defect (fixed)

chutney triggers tor warnings about ExitRelay not being set

Reported by: teor Owned by:
Priority: Medium Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords: SponsorS testing
Cc: Actual Points:
Parent ID: #17011 Points:
Reviewer: Sponsor:

Description

All authorities including the bridge authority, all relays:

../chutney/net/nodes/000a/info.log:Sep 15 23:24:25.144 [warn] Tor is running as an exit relay with the default exit policy. If you did not want this behavior, please set the ExitRelay option to 0. If you do want to run an exit Relay, please set the ExitRelay option to 1 to disable this warning, and for forward compatibility.
../chutney/net/nodes/000a/info.log:Sep 15 23:24:25.144 [warn] In a future version of Tor, ExitRelay 0 may become the default when no ExitPolicy is given.

This affects #17011 when we are trying to force IPv6-only exit connections.

This may also indicate a misconfiguration, or simply me (teor) forgetting ExitRelay 0/1 in the torrc templates.

Child Tickets

Change History (4)

comment:1 Changed 3 years ago by nickm

Owner: nickm deleted
Status: newassigned

Remove myself as chutney ticket owner. Default owners are trouble.

comment:2 Changed 3 years ago by nickm

Status: assignednew

comment:3 Changed 2 years ago by teor

Severity: Normal

This is a bug in chutney: it meant that all relays were exit relays with the default exit policy. (Is this really what we want in tor?)

This can be fixed, but the IPv4/IPv6 config triggers a warning that ExitRelay is defined multiple times. See #21371 for a solution that filters out bug messages.

comment:4 Changed 2 years ago by teor

Resolution: fixed
Status: newclosed

Fixed in 12eceea.

Note: See TracTickets for help on using tickets.