Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,067
    • Issues 1,067
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 19
    • Merge Requests 19
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Core
  • Tor
  • Issues
  • #40243

Closed
Open
Opened Jan 15, 2021 by David Goulet@dgoulet😈Owner

dirauth: IPv6 sybil detection should not use /64

Offending commit is d07f17f6

Basically, a /64 is a network given to end users that is the minimum routable on the Internet iirc.

If dirauth sybil protection uses that, then all relays on the same network won't be able to join the network. At this moment, moria1 is rejecting 435 relays based on that behavior because at least 3 relays are in the same network and thus all get considered as sybil.

The correct thing to do here I believe is that we should use /128 as in match the address only, not the network. Path selection is using /32 here so it is OK to allow multiple relays from the same network as we do in IPv4, just not in the same path.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.4.5.x-stable
Milestone
Tor: 0.4.5.x-stable (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/core/tor#40243