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 326
    • Issues 326
    • 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
  • #33899
Closed
Open
Issue created Apr 14, 2020 by teor@teor

Allow IPv6 addresses to be canonical

In legacy/trac#17604 (moved), we allowed IPv6 connections to set is_canonical_to_peer. But we did not let them set is_canonical.

So channel_tls_process_netinfo_cell() handles IPv6 addresses, but connection_or_check_canonicity() does not.

This inconsistency could be one cause of the logging issues in legacy/trac#24841 (moved).

We should allow IPv6 connections to be canonical. We should also do some cleanup of the related connection address logging in legacy/trac#33898 (moved).

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