Doxx/Darkflare: DarkFlare TCPoCDN (TCP over CDN)
github.com
github.com
Proxying projects utilising HTTP/TLS are popular in the anti-censorship community (discussion board: https://github.com/net4people/bbs) and there are many variants of it; ex:
- KCP (over UDP): https://github.com/xtaci/kcp-go
Apparently Cloudflare, since a few weeks ago, has started flagging traffic bound to/from proxies as DDoS vectors: https://github.com/net4people/bbs/issues/429
The author is pretty naive. There is a reason why Google was left out of the list, in the 2010s people argue "Google is too important and China never dare to block it" then google's whole IP range is blocked.
Amazon Cloudfront, Akmai, Fastly are also (partially) blocked and barely working.
IMHO cleve tricks like "domain fronting" is just freebooting
What do you mean by "freebooting"?
We added domain fronting support to the OpenConnect TLS-VPN client _in 2022_ because it is still working and useful for many people working in censored countries and environments. https://gitlab.com/openconnect/openconnect/-/merge_requests/...
That's a big "still" and you don't loose anything in case the real owner of the "fronted" domain suffers loss.
https://en.m.wikipedia.org/wiki/Filibuster_(military)
Private attempts to meddle in the security and interests of states.
Install a cloudflared tunnel on your remote server, configure it to forward traffic to that server's hosts proxy server(maybe Shadowsocks) using Zero Trust dashboard, and run the following command on your local computer:
cloudflared access tcp --hostname some.your-domain.tld --url localhost:8080
Then localhost:8080's traffic will be forwarded to cloudflareds' host, the whole traffic is using HTTP2 so might look legitimate to Firewall.
For example if using Shadowsocks on server, your Shadowsocks's local client can connect to localhost:8080 as server to forward traffic.
The use case is to relay WireGuard over TCP/CF in a restrictive network, confirmed to work in China, obviously not too fast.
I don’t get why headers and requests need to be spoofed if all traffic is over https?
It's obfuscation at best. I'm not sure the encrypted traffic will look particularly php-ish for example. Compressed formats might look vaguely passable.
I can't see any stenography code or libraries in the repo.
> Also, State (sponsored) Actors are certificate authorities.
To generate a fake certificate as a CA you have to either put it in the Certificate Transparency log, in which case everyone will notice, or don't, in which case browsers will notice (they know what top sites' certificates are supposed to look like) and your CA will get shut down.
Because the traffic is to a CDN endpoint (like Cloudflare) which expects it to be a HTTP message.
Services like Cloudflare, Akamai Technologies, Fastly, and Amazon CloudFront are not only widely accessible but also integral to the global internet infrastructure. In regions with restrictive networks, alternatives such as CDNetworks in Russia, ArvanCloud in Iran, or ChinaCache in China may serve as viable proxies. These CDNs support millions of websites across critical sectors, including government and healthcare, making them indispensable.
Blocking them risks significant collateral [commercial, commerce] damage, which inadvertently makes them reliable pathways for bypassing restrictions."
(There's also TCP/IP (Internet) via HAM radio (packet radio) and/or StarLink (or more broadly, satellite Internet)...)
Observation: If a large enough commercial corporation has an interest relating to commerce (in whatever area), then if that commerce conflicts with a government block (foreign or domestic) of whatever sort, then the large commercial interest, given enought time, will usually (*) win (they can usually hire better Lawyers, foreign or domestic...)
(*) But not always...
I get the idea and the spirit behind using ham radio to evade censorship, but...
- you're not allowed to run encrypted content over ham packet radio, at least by regulations, plain HTTP is fine but anything SSL is not... don't be a dick and ruin the fun for everyone else.
- ham radio comms is, outside of emergencies such as widespread blackouts or natural disasters, supposed to only be between ham radio operators themselves - no message-passing for others.
- at least in the long-range bands that you'd actually use for cross-country communications, bandwidth is scarce - and you may disturb a lot of people by doing that, or by just blasting around with huge transmitters... Monday late evening in Germany, try to listen in on 80m, there's so damn many Russians on there with extremely powerful transmitters.
Ham radio frequencies are scarce enough as it is and politicians, particularly in authoritarian countries, already aren't happy about it (in North Korea, for example, it's banned and it's one of the rarest countries to DX with). Please don't make life for hams more complex than it already is by abusing what it stands for.
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-...
We've been running that in prod for several years without any issues, also going through cloudflare