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

Closed (moved)
Open
Created Oct 04, 2011 by Trac@tracbot

Bridge easily detected by GFW

I tried to setup a bridge relay in USA and access it from China. But it seems their communication can be detected very soon and got filtered by the GFW.

At first I thought it's because the address of my bridge relay got published and leaked to the GFW staffs. But even I set PublishServerDescriptor to 0 in the torrc of bridge the blockade still occurs.

Every bridge relay I setup can only live 1~10 minutes before they got blocked and were no longer accessible in China, used the telnet utility for confirming that.

When the blockade occurs, not only bridges but also normal relays were blocked.

If I change the bridge port (like from 443 to 444) then it can be connected again before the next blockade occurs after 1~10 minutes.

I tried the both stable 0.2.1.x and alpha (0.2.3.5-alpha) release of tor and they were all vulnerable.

Was it a new attack to block tor traffic?

Trac:
Username: hrimfaxi

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