Re:QUIC and HTTP/3 Support Now in Firefox Nightly and Beta
by CameronNemo on Friday April 16, 2021 @04:47PM
(#26838902)
Can you not disguise the wireguard tunnels as something else? E.g. just set the destination/listen port as 443/UDP? Or 53, 123.
[ Parent
| on HN ]
Re:QUIC and HTTP/3 Support Now in Firefox Nightly and Beta
by judge2020 on Friday April 16, 2021 @04:58PM
(#26839008)
While not usual for places like coffee shops, i've seen cruises and hotels do DPI since probably a sizable amount of revenue can be generated from fast wifi access or by unblocking all sites.
Re:QUIC and HTTP/3 Support Now in Firefox Nightly and Beta
by CameronNemo on Friday April 16, 2021 @05:31PM
(#26839296)
Yep that is always an issue. Not sure how a hypothetical QUIC tunnel would avoid that, though. Would appreciate any info you can provide on mitigating deep packet inspection blocking techniques.
Re:QUIC and HTTP/3 Support Now in Firefox Nightly and Beta
by grishka on Friday April 16, 2021 @11:07PM
(#26841299)
I've been tempted to write a quick-and-dirty websocket tunnel for quite some time. Let's see how they DPI any of that without breaking anything else.
Re:QUIC and HTTP/3 Support Now in Firefox Nightly and Beta
by shawnz on Saturday April 17, 2021 @12:27AM
(#26841579)
Why not just use an HTTP CONNECT proxy running over HTTPS?
Re:QUIC and HTTP/3 Support Now in Firefox Nightly and Beta
by grishka on Saturday April 17, 2021 @05:47AM
(#26842955)
You could do that? Well, you probably could.
But there are some "proactive" DPIs that make a request themselves before letting you through. Would this protect against that? It's easy to set up a regular web server that would serve what everyone would see as an ordinary personal website, except when you make a request to a secret URL.
Re:QUIC and HTTP/3 Support Now in Firefox Nightly and Beta
by shawnz on Saturday April 17, 2021 @09:40AM
(#26844183)
You could require authentication (and as other posters pointed out, make sure to spoof any wrong authentications for maximum deniability).
It is also simple to serve some pages over HTTP alongside the proxy functionality so that the server appears to be a typical web server. Just turn on mod_proxy_connect in addition to your existing httpd configuration if you use Apache for example.
I use this method on my domains, although I've never tried using it from within e.g. China