Skip to content
GitLab
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
  • #8676
Closed
Open
Issue created Apr 10, 2013 by George Kadianakis@asn

Research an HTTP pluggable transport that actually uses a browser and a web server

Research like www.cs.utexas.edu/~shmat/shmat_oak13parrot.pdf makes it even more clear that it's worth exploring the possibility of actually using the software you are trying to emulate. That is, if you are trying to look like Skype, you better use the Skype binary. If you want to look like HTTP, you better use a browser on the client-side and a web server on the server-side.

We should look whether we can use stuff like Webkit to write a client-side transport, and a web server like nginx or apache to write its server-side.

Assignee
Assign to
Time tracking