Awesome

DarkFlare - TCP-over-CDN Tunnel

A stealthy command line tool to create TCP-over-CDN(http) tunnels that keep your connections cozy and comfortable. Now with public test relay servers!

Join the Discord server for support and discussion: https://discord.gg/7wVKeP88

🤔 What is this sorcery?

DarkFlare is a clever little tool that disguises your TCP traffic as innocent HTTPS requests, letting them pass through corporate firewalls like a VIP at a nightclub. It's like a tunnel, but with more style and less dirt.

It has two parts: a client-side proxy (darkflare-client) that encodes TCP data into HTTPS requests and sends it to a Cloudflare-protected domain, and a server-side proxy (darkflare-server) that decodes the requests and forwards the data to a local service (like SSH on port 22). It’s protocol-agnostic, secure, and uses Cloudflare's encrypted infrastructure, making it stealthy and scalable for accessing internal resources or bypassing network restrictions.

When using this remember the traffic over the tunnel is only as secure as the Cloudflare protection. Use your own encryption.

🧱 Why CDNs?

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 damage, which inadvertently makes them reliable pathways for bypassing restrictions.

⛓️‍💥 Stop Network Censorship

Internet censorship is a significant issue in many countries, where governments restrict access to information by blocking websites and services. For instance, China employs the "Great Firewall" to block platforms like Facebook and Twitter, while Iran restricts access to social media and messaging apps. In Russia, authorities have intensified efforts to control information flow by blocking virtual private networks (VPNs) and other tools that citizens use to bypass censorship.

AP NEWS In such environments, a tool that tunnels TCP traffic over HTTP(S) through a Content Delivery Network (CDN) like Cloudflare can be invaluable. By disguising restricted traffic as regular web traffic, this method can effectively circumvent censorship measures, granting users access to blocked content and preserving the free flow of information.

                                FIREWALL/CENSORSHIP
                                |     |     |     |
                                v     v     v     v

[Client]──────┐                ┌──────────────────┐                ┌─────────[Target Service]
              │                │                  │                │       (e.g., SSH Server)
              │                │   CLOUDFLARE     │                │tcp      localhost:22
              │tcp             │     NETWORK      │                │
[darkflare    │                │                  │                │ [darkflare
 client]──────┼───HTTPS───────>│ (looks like      │─-HTTPS-───────>│  server]
localhost:2222│                │  normal traffic) │                │ :8080
              │                │                  │                │
              └────────────────┼──────────────────┼────────────────┘
                               │                  │
                               └──────────────────┘

Flow:
1. TCP traffic ──> darkflare-client
2. Wrapped as HTTPS ──> Cloudflare CDN (or any CDN)
3. Forwarded to ──> darkflare-server
4. Unwrapped back to TCP ──> Target Service

CA Root Notes

In some cases the direct server might fail TLS. If that happens you can use the CDN server or make sure you have the CA certs:

For Debian-based Systems (e.g., Ubuntu)

sudo apt install ca-certificates

For Red Hat-based Systems (e.g., CentOS, Fedora)

sudo yum install ca-certificates

Usecases

ssh, rdp, or anything tcp to bypass restrictive firewalls or state controled internet.

Tunneling ppp or other vpn services that leverage TCP.

darkflare-server can launch applications like sshd or pppd. Note that there are issues with host keys and certificate validation on sshd if you don't configure it properly.

Linux's popular pppd daemon will also not run as non-root in some cases, which would require a more complex configuration with sudo.

Breaking past blocked sites!

How to use NordVPN over TCP

NordVPN

Download the OpenVPN client (cli is better)
Under Manual setup in your NordVPN web account download the .ovpn file for TCP
Also in Manual setup select username and password authentication.
Edit the .ovpn file and change the IP and port to your darkflare server IP and Port.
Configure darkflare-server to use the IP and port defined in the .ovpn file.
Import the .ovpn file to OpenVPN and setup your username and password.

I did provide an ./examples/nordvpn.ovpn for you to use. Also two scrips for up/down to fix some of the routing issues.

Using the OpenVPN commandline client you can embed the username, password, and it runs the scripts properly for you:

& openvpn --config 127.0.0.1.tcp2222.ovpn --script-security 2

Note: OpenVPN by default screws up the default gateway/route. For testing purposes I added: pull-filter ignore "redirect-gateway" to the .ovpn file. That allows me to force the tunnel to not change the routing. The routing can be fixed by the OpenVPN-up.sh and OpenVPN-down.sh scripts. This is due to the fact that the VPN is connecting to the whole CDN range of IP addresses.

🔐 Few Obscureation Techniques

Requests are randomized to look like normal web traffic with jpg, php, etc... with random file names.

Client and server headers are set to look like normal web traffic.

If you have other ideas please send them my way.

🌩️ Cloudflare Configuration

Add your new proxy hostname into a free Cloudflare account.

Setup your origin rules to send that host to the origin server (darkflare-server) via the proxy port you choose.

I used 8080 with a Cloudflare proxy via HTTP for the firs test. Less overhead.

✨ Features

Sneaky TCP Tunneling: Wraps your TCP connections in a fashionable HTTPS outfit
Cloudflare Integration: Because who doesn't want their traffic to look like it's just visiting Cloudflare?
Debug Mode: For when things go wrong and you need to know why (spoiler: it's always DNS)
Session Management: Keeps your connections organized like a Type A personality
TLS Security: Because we're sneaky, not reckless
Client-controlled destination addressing: The destination (-d) is now specified on the client side and securely transmitted to the server
Base64 encoded destination transmission: The server no longer requires a destination parameter (-d has been removed)

🚀 Quick Start

Installation

Download the latest release from the GitHub Releases page
- Choose the appropriate binary for your system:
  - darkflare-client-darwin-arm64 - macOS Apple Silicon
  - darkflare-client-darwin-amd64 - macOS Intel
  - darkflare-client-linux-amd64 - Linux x64
  - darkflare-client-windows-amd64.exe - Windows x64
  - darkflare-server-* - corresponding server binaries
Verify the checksums against checksums.txt (recommended)
Make the binaries executable (Unix systems):

chmod +x darkflare-client-* darkflare-server-*

Running the Client

./darkflare-client -l 2222 -t https://cdn.miami.us.doxx.net:443 -d <my ssh server>:22

Or with direct mode:

./darkflare-client -l 2222 -t https://direct.miami.us.doxx.net:443 -d <my ssh server>:22

Add -debug flag for debug mode

Notes

If you want to debug and go directly to the psudo server you can use the -allow-direct flag on the server.

You can replace the doxx.net server with your own and setup your own server:

Running the Server

# HTTPS Server (recommended for production)
./darkflare-server -o https://direct.miami.us.doxx.net:443 -c /path/to/cert.pem -k /path/to/key.pem

# HTTP Server (for testing)
./darkflare-server -o http://direct.miami.us.doxx.net:8080 -allow-direct

Notes

The -allow-direct flag allows direct connections without Cloudflare headers (not recommended for production)
Debug mode (-debug) provides verbose logging of connections and data transfers
Under SSL/TLS configuration in Cloudflare you need to set ssl encryption mode to Full.

SSL/TLS Certificates

For HTTPS mode, you'll need to obtain origin certificates from Cloudflare:

Log into your Cloudflare dashboard
Go to SSL/TLS > Origin Server
Create a new certificate (or use an existing one)
Download both the certificate and private key
When starting the server in HTTPS mode, provide both certificate files:

Note: Keep your private key secure and never share it. The certificate provided by Cloudflare is specifically for securing the connection between Cloudflare and your origin server.

Testing the Connection

ssh user@localhost -p 2222

⚠️ Security Considerations

Always use end-to-end encryption for sensitive traffic
The tunnel itself provides obscurity, not security
Monitor your Cloudflare logs for suspicious activity
Regularly update both client and server components

⚠️ Disclaimer

This tool is for educational purposes only. Please don't use it to bypass your company's firewall - your IT department has enough headaches already.

🤝 Contributing

Found a bug? Want to add a feature? PRs are welcome! Just remember:

Keep it clean
Keep it clever

📜 License

MIT License - Because sharing is caring, but attribution is nice.

Built with ❤️ and a healthy dose of mischief

Join the Discord server for support and discussion: https://discord.gg/7wVKeP88