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
  • #7636

Closed
Open
Opened Dec 04, 2012 by Trac@tracbot

setting socks port for TBB in OS X

I'm running the latest Tor Browser Bundle (2.3.25-1) on OS X 10.7. In previous TBB's it was possible to change the SocksPort on the bundle's version of Tor, which made it easier to configure other applications to use the TBB's instance of Tor as a proxy. There appears to be no working mechanism to do this in the current version.

Here are some of the failed ways I have tried to set the SOCKS port:

  1. edit the torrc via Vidalia's preferences: Vidalia > Settings > Advanced > Edit current torrc

This fails with the bug described in tickets #6147 (closed), #7299 (closed).

  1. edit the torrc manually at its location in path/to/TorBrowser_en-US.app/Library/Vidalia/torrc

This has no effect on the running configuration. Revisiting the torrc via "Edit current torrc" in the Preferences shows the changes that have been made, but they do not affect the process. It still logs that it is opening the SOCKS port and control port on IP:0 (randomly chosen).

  1. edit the vidalia.conf manually (same dir as torrc). Set AutoControl=false (with the previous changes to the torrc), recommended as a workaround in #4379 (closed). Still no change.

It appears that one of the above tickets may be close to resolution; others suggest non-functional workarounds or are over a year old. If this ticket is unnecessary please feel free to delete or mark as a dupe - I just wanted to make sure people are aware of some highly unexpected behavior (especially the ignoring of the torrc, which I find to be quite disturbing).

Trac:
Username: garrettr

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#7636