httptunnel
iodine
httptunnel | iodine | |
---|---|---|
3 | 58 | |
397 | 5,794 | |
- | - | |
2.7 | 5.1 | |
12 months ago | 5 months ago | |
C | C | |
GNU General Public License v3.0 only | ISC License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
httptunnel
-
Actual SSH over HTTPS
Corkscrew works for a specific use case:
1. you're behind an HTTP proxy, and
2. the HTTP proxy support the CONNECT method
Around 20 years ago I did a short contract which had #1 but not #2. Thankfully, there's a tool for this, too. Of course it requires some set up on the server side:
https://github.com/larsbrinkhoff/httptunnel
- How would a network be blocking vpns
-
(Reverse) SSH tunnel from work over HTTP(s) proxy to a home computer behind NAT?
Maybe this can help? https://github.com/larsbrinkhoff/httptunnel
iodine
-
Show HN: This Website Is Hosted on DNS
Reminds me of using https://code.kryo.se/iodine/ ( DNS tunnel ) and a empty prepaid card...
-
DNS Exfiltration Tool
Obligatory dns tunnel software for exfil. It is super noisy if you do dns querylogging, so I'd not use it for anything major, but it is a fun research tool.
https://github.com/yarrick/iodine
-
Fun with DNS TXT Records
It's worth noting that you (re) invented what iodine does: https://code.kryo.se/iodine/
-
WiFi without internet on a Southwest flight
(https://github.com/yarrick/iodine)
It’s slow, but it works and is a handy “last resort” tool.
-
Russia starts blocking VPN at the protocol (WireGuard, OpenVPN) level
While working in an environment where VPN connections were pretty much all blocked⁰ a friend of mine had success using https://guacamole.apache.org/ to access a remote machine¹. Not quite the same as a direct VPN connection but worth a try if nothing else functions, it looks enough like normal HTTPS traffic that he got away with it.
To keep your wireguard setup more as-is, you could try https://kirill888.github.io/notes/wireguard-via-websocket/ to tunnel that via a web server. In fact https://github.com/erebe/wstunnel which that uses could be used just as well with any other UDP based VPN.
I once tinkered with https://github.com/yarrick/iodine and successfully connected to resources over the wireless on a train, bypassing its traffic capture and sign-up requirement, so that might be an option, though I think fully blocking external DNS is more common now so this is less likely to work²³.
--
[0] practically only HTTP(S) permitted, not even SSH, DPI in use that detected just using SSH or OpenVPN over port 443
[1] NOTE: be careful breaching restrictions like this, you are at risk of an insta-sacking if discovered, or worse if operating in some securiry environments!
[2] and the latency when it does work is significant!
[3] and that much traffic over port 53 might get noticed by the heuristics of data exfiltration scanner, encouraging sysadmins to notice and implement a way to block it
-
Show HN: File distribution over DNS: (ab)using DNS as a CDN
There's also iodine, a C program that tunnels IPv4 packets over DNS. Useful for bypassing captive portals on wifi, since DNS usually isn't restricted.
https://github.com/yarrick/iodine
Regarding cloudflare DNS over HTTPS: It could be that it tries to server data encoded as JSON, which is impossible in JSON. Some control characters and bytes 128-255 cannot be represented as JSON strings.
-
Show HN: Use DNS TXT to share information
A regular proxy on port 53 might work? Is it necessary to actually use DNS?
Otherwise there's https://github.com/yarrick/iodine
- Anything can be a message queue if you use it wrongly enough
-
help with choosing a VPN to host (I'll explain)
Well, you're really exhausting your options here (and possibly your IT department's patience). Iodine would still be an option, it creates a tunnel through DNS traffic. Nearly impossible to block/filter out but you shouldn't expect a lot of bandwidth. Try it out! Although if you're only going to use low-bandwidth applications through the tunnel anyway you might as well use your own mobile data plan instead of your school's WLAN.
- DNS blacklisting in enterprise