Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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.

  • Legacy
  • TracTrac
  • Issues
  • #6822

Closed
Open
Opened Sep 12, 2012 by Andrew Lewman@andrew

TBB x86_64 2.3.22-alpha-1 uses hardcoded control port

The latest tor-browser-gnu-linux-x86_64-2.3.22-alpha-1-dev-en-US.tar.gz has a hardcoded 9051 control port. This conflicts with system tor if you have one. Previous versions used dynamic control and socks port assignments on start.

For example, tor-browser-gnu-linux-x86_64-2.3.20-alpha-1-dev-en-US.tar.gz works correctly.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#6822