Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P pluggable transports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • pluggable transports
  • Issues
  • #12614

Closed
Open
Created Jul 13, 2014 by Ximin Luo@infinity0

Design a good way to pass transport options to child PTs

Client transports get their k=v options from the SOCKS parameters, which is given in the Bridge line. Server transports get their k=v options from ServerTransportOptions.

We need to define ways for fog to pass these options down to the relevant child.

For example, one basic syntax would be, if fog receives an option of the form "fog-child-n-k=v", it passes "k=v" as the option (either SOCKS or ServerTransportOptions) down to the nth child PT in the chain. (This may not be the best idea; the consequences should be examine before we commit to this.)

This must be documented as a public API of fog.

Assignee
Assign to
Time tracking