Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #15203

Closed (moved)
(moved)
Open
Created Mar 09, 2015 by Trac@tracbot

Incorrect port numbers hardcoded in config.c for moria1

While checking out the hardcoded directory authorities, I noticed that the OR and DIR port number for the first one, "moria1", do not correspond to the ones given by https://atlas.torproject.org/#search/128.31.0.39:

   "moria1 orport=9101 "
      "v3ident=D586D18309DED4CD6D57C18FDB97EFA96D330566 "
      "128.31.0.39:9131 9695 DFC3 5FFE B861 329B 9F1A B04C 4639 7020 CE31",

https://gitweb.torproject.org/tor.git/tree/src/or/config.c#n853

According to atlas, the ports should be ORport=9005 and DirPort=9035 instead of ORport=9101 and DirPort=9131.

This might explain why my attempt to connect to the Tor network using a newly extracted TorBrowser, with my firewall blocking ports 80 and 443 failed.

P.S.: I think it might be worth adding a few more directory authorities with common ports like ssh,imap,smtp,ftp,etc for places with extreme firewalls. :) Or maybe add the directory info in the tor browser bundle? Is it possible to create/download "cached-microdescs" files from the tor atlas?

Trac:
Username: lom

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