Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C Chutney
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • Chutney
  • Issues
  • #17090
Closed
Open
Issue created Sep 15, 2015 by teor@teor

chutney triggers tor warnings about ExitRelay not being set

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 legacy/trac#17011 (moved) 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.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking