Changes between Version 3 and Version 4 of doc/PluggableTransports/ideas


Ignore:
Timestamp:
Mar 21, 2018, 11:42:44 PM (6 months ago)
Author:
dcf
Comment:

Link to my post about DNS-over-HTTPS.

Legend:

Unmodified
Added
Removed
Modified
  • doc/PluggableTransports/ideas

    v3 v4  
    2727   * important internet infrastucture: ntp sql radius hadoop mongodb
    2828   * [[DnsPluggableTransport|DNS   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 [http://code.kryo.se/iodine/ iodine] and [http://wiki.skullsecurity.org/Dnscat dnscat]. Probably requires a reliability layer and periodic polling by the client.
    29      * [https://developers.google.com/speed/public-dns/docs/dns-over-https DNS-over-HTTPS] (note: Google is logging your DNS request and IP information)
     29     * [https://datatracker.ietf.org/doc/draft-ietf-doh-dns-over-https/?include_text=1 DNS-over-HTTPS] summary of idea: https://groups.google.com/forum/#!topic/traffic-obf/ZQohlnIEWM4
     30       (note: Google/Cloudflare/whoever is logging your DNS request and IP information)
    3031 * Provide a long and relativly high bandwidth flow to hide data in (See the note regarding dead parrot attacks)
    3132   * ventrillo, teamspeak and mumble