Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 328
    • Issues 328
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #33819
Closed
Open
Issue created Apr 05, 2020 by teor@teor

Make clients and bridges send IPv6 extends by default in Tor 0.4.5

If #33818 (closed) is included in Tor 0.4.4, the relays will send IPv6 extends by default. But clients and bridges won't, for anonymity reasons.

By the time 0.4.5 is released, a large number of clients and bridges will be on 0.4.4. So it will be safe for clients and bridge to send IPv6 extends.

Here's what we need to do to change the default:

  • set ExtendByIPv6ORPort=1 in the consensus, and
  • set ExtendByIPv6ORPort 1 as the default in Tor.

To avoid confusion, clients and bridges will send IPv6 extends, but they won't initiate outbound IPv6 connections to relays. For more details, see legacy/trac#33818 (moved) and ExtendAllowIPv6Addresses.

Edited Aug 18, 2020 by David Goulet
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking