Currently slipgate chains NaiveProxy + SSH as its tunnel backend. In environments where port 443 and SSH are fully blocked but DNS (UDP/53) remains open, this chain fails entirely.
Please consider adding support for MasterDnsVPN and/or StormDNS as an alternative DNS-based tunnel backend:
Both use ARQ-based DNS tunneling with a local SOCKS5 endpoint, making them well-suited as a drop-in inner tunnel when TCP/443 and SSH are unavailable. This would fill the one remaining censorship gap in slipgate's coverage.
Currently slipgate chains NaiveProxy + SSH as its tunnel backend. In environments where port 443 and SSH are fully blocked but DNS (UDP/53) remains open, this chain fails entirely.
Please consider adding support for MasterDnsVPN and/or StormDNS as an alternative DNS-based tunnel backend:
Both use ARQ-based DNS tunneling with a local SOCKS5 endpoint, making them well-suited as a drop-in inner tunnel when TCP/443 and SSH are unavailable. This would fill the one remaining censorship gap in slipgate's coverage.