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

Closed (moved)
Open
Opened Sep 18, 2015 by Trac@tracbot

pluggable transport ideas

i just leave some ideas here for brainstorming and discussion: protocols that could be used:

bgp and other routing protocols: its important for the infrastructure and was even used to enforce censorship. thus it might be too hot to touch for censors.

various streaming protocols: internet radio or video streaming provides an unsuspicious data flow.

rdp, rfb(vnc) and teamviewer: a censor might hesitate to block the tech support for their goverment and industry

industrial, telemetry and military protocols(scada,lonworks,...):might be too hot to touch as well

mail: pop3, smpt, imap or send mails over legit mail servers

ventrillo, teamspak and mumble: same as streaming

others: ntp sql radius hadoop mongodb

Trac:
Username: elypter

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
Reference: legacy/trac#17104