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,078
    • Issues 1,078
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 24
    • Merge Requests 24
  • 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
  • #25935

Closed
Open
Created Apr 26, 2018 by Trac@tracbot

Allow DA address to be specified as FQDN

It would be very helpful, particularly in sandbox situations, to specify the Directory Authority by FQDN hostname instead of by IP address. This would allow us to defer picking an actual IP address until the simulation is started, and even to use some "in-game" DNS facility to figure out the actual address after the simulation is launched.

Right now, specifying a FQDN for the "DirAuthority" config file entry even partially works already: if the FQDN happens to start with a digit, it is correctly resolved internally using available DNS resolver infrastructure :)

The first attached patch makes that work in all cases (even when the FQDN hostname does not begin with a digit).

The second attached patch allows FQDNs to be inserted into DA certs created using tor-gencert, and correspondingly resolved when a client parses the downloaded DA certificate.

I realize there is ongoing work to refactor parsing the DA config entry (ticket legacy/trac#17224 (moved)), so please consider this patch set either independently on its own merits or as part of that larger effort. In the first case, I'd be happy to redo and resubmit the patches based on review/feedback.

Trac:
Username: somlo

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.3.5.x-final
Milestone
Tor: 0.3.5.x-final
Assign milestone
Time tracking
None
Due date
None