Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #15213
Closed (moved) (moved)
Open
Issue created Mar 10, 2015 by Federico Ceratto@federico

DNS tunneling transport (like iodine, dnscat)

DNS-based pluggable transport.

Encode data in recursive DNS queries and responses. Your local recursive resolver sends your packets to the right place. A DNS bridge would be an authoritative name server for a particular domain; users would configure a domain rather than an IP address in their Bridge lines. Tools already exist to do DNS tunneling, for example ​iodine and ​dnscat. Probably requires a reliability layer and periodic polling by the client.

Provides a way for users behind restrictive firewalls to connect to Tor at the expense of speed.

Mailing list discussions: [tor-dev] obfsproxy dns transport ​https://lists.torproject.org/pipermail/tor-dev/2014-February/006250.html (Feb 2014)

using OzymanDNS to access Tor via DNS ​https://lists.torproject.org/pipermail/tor-talk/2006-January/007124.html (Jan 2006)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking