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
  • Activity
  • Create a new issue
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #11395

Closed (moved)
Open
Created Apr 03, 2014 by tails-developers@tails-developers

Tor launcher should not allow impossible configurations: eg. restricted firewall + obfs3 bridges

In TBB 3.6-beta-1 for example, if I configure a firewall restricted to ports 80 and 443, and ask to use the preconfigured obfs3 bridges, then the process bar on the "connecting" windows doesn't move and Tor never connects.

If this configuration combination is not possible in Tor, it shouldn't be allow to set via Tor launcher in the first place.

This issue was initially reported on bug tracker: https://labs.riseup.net/code/issues/6985

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