Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
H
HTTPT
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Jobs
  • 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.

  • The Tor Project
    • A
      Anti-censorship
  • Pluggable Transports
  • HTTPT
  • Issues
  • #5

Closed
Open
Created Sep 10, 2020 by Philipp Winter@phwMaintainer

Teach HTTPT to register itself to rdsys and forward traffic to a Tor bridge

This is a child issue of #1.

If we run an HTTPT server independently from a Tor bridge, we need to teach it how it can register itself to rdsys, so we can hand out HTTPT proxies to users. Over at tpo/anti-censorship/rdsys#4 (closed), we are brainstorming an API that allows systems like HTTPT to register themselves.

In addition to the registration mechanism, we need to teach HTTPT to forward traffic to a bridge. For now, we may want to set up a dedicated and centralised bridge, just like the one we are using in Snowflake.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None