Skip to content
GitLab
  • Menu
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 43
    • Issues 43
    • 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
  • #40013
Closed
Open
Created Dec 16, 2020 by juga@juga

Template relay-non-exit.tmpl does generate exits

I assume this is the template to use to generate non-exits, if not this is probably not an issue.

The network hs-v2-min uses this template. I start the network and try to obtain the relays without the EXIT flag:

from stem import Flag
from stem.control import Controller


c = Controller.from_port(port=8000)
c.authenticate()
cons = c.get_network_statuses()
[(rs.nickname, rs.flags) for rs in cons if Flag.EXIT not in rs.flags]
>>> []

But all relays have the exit flag.

The generated torrc has ExitRelay 0, so i guess that it must be some other option that is making the relays to be flagged as exits?

Is there other way to generate non-exits?

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