Daze

Daze is a software that helps you pass through firewalls, in other words, a proxy. It uses a simple yet efficient protocol, ensuring that you never get detected or blocked.

Getting Started

Daze is designed as a single-file application. First, compile or download daze:

$ git clone https://github.com/mohanson/daze
$ cd daze

# On Linux or macOS
$ ./cmd/develop.sh
# On Windows
$ ./cmd/develop.ps1

The build results will be saved in the bin directory. You can keep this directory, and all other files are not required.

Daze is dead simple to use:

# Server side
# You need a machine that can access the Internet, and enter the following command:
$ daze server -l 0.0.0.0:1081 -k $PASSWORD

# Client side
# Use the following command to link your server(replace $SERVER with your server IP):
$ daze client -s $SERVER:1081 -k $PASSWORD
# Now, you are free to visit the Internet
$ curl -x socks5://127.0.0.1:1080 google.com

Using Daze for Different Platforms

Daze is implemented in pure Go language, so it can run on almost any operating system. The following are some of the browsers/operating systems commonly used by me:

Android

0. Cross-compile daze for Android: GOOS=android GOARCH=arm64 go build -o daze github.com/mohanson/daze/cmd/daze
1. Push the compiled file to the phone. You can use adb or create an HTTP server and download daze with wget in termux.
2. Run daze client -l 127.0.0.1:1080 ... in the termux.
3. Set the proxy for phone: WLAN -> Settings -> Proxy -> Fill in 127.0.0.1:1080

Chrome

Chrome does not support setting proxies, so a third-party plugin must be used. Proxy SwitchyOmega works very well.

Firefox

Firefox can configure a proxy in Connection Settings -> Manual proxy configuration -> SOCKSv5 Host=127.0.0.1 and Port=1080. If you see an option Use remote DNS on the page, check it.

Network Model And Concepts

Daze's network model consists of 7 components:

+-------------+        +-------------+        +----------+        +-------------+        +-----------+
| Destination | <----> | Daze server | <----> | Firewall | <----> | Daze client | <----> |    User   |
+-------------+        +------+------+        +----------+        +-------------+        +-----------+
                              |                                          |                     |
                              +------------- Middle Protocol ------------+-- Client Protocol --+

• Destination: The destination is an internet service provider, for example, google.com.
• Daze Server: A Daze server is an instance that runs using the command daze server.
• Firewall: A firewall is a network security system that monitors and controls incoming and outgoing network traffic based on pre-determined security rules.
• Daze Client: A Daze client is an instance that runs using the command daze client.
• User: A user is a browser or any other application attempting to access the destination.
• Middle Protocol: The middle protocol is the communication protocol between the Daze server and Daze client. Data is encrypted and obfuscated to bypass firewalls.
• Client Protocol: The client protocol is the communication protocol between the Daze client and the user.

Protocols

Client Protocols

The Daze client implements five different proxy protocols in one port. These protocols are HTTP Proxy, HTTPS Tunnel, SOCKS4, SOCKS4a, and SOCKS5.

# HTTP Proxy
$ curl -x http://127.0.0.1:1080    http(s)://google.com
# HTTPS Tunnel
$ curl -x http://127.0.0.1:1080    http(s)://google.com
# SOCKS4
$ curl -x socks4://127.0.0.1:1080  http(s)://google.com
# SOCKS4a
$ curl -x socks4a://127.0.0.1:1080 http(s)://google.com
# SOCKS5
$ curl -x socks5://127.0.0.1:1080  http(s)://google.com

Why can one port support so many protocols? Because it's magic!

Middle Protocols

Daze currently has 4 middle protocols.

Ashe

The default protocol used by Daze is called Ashe. Ashe is a TCP-based cryptographic proxy protocol designed to bypass firewalls while providing a good user experience.

Please note that it is the user's responsibility to ensure that the date and time on both the server and client are consistent. The Ashe protocol allows for a deviation of up to two minutes.

Baboon

Protocol baboon is a variant of the ashe protocol that operates over HTTP. In this protocol, the daze server masquerades as an HTTP service and requires the user to provide the correct password in order to gain access to the proxy service. If the password is not provided, the daze server will behave as a normal HTTP service. To use the baboon protocol, you must specify the protocol name and a fake site:

$ daze server ... -p baboon -e https://github.com
$ daze client ... -p baboon

Czar

Protocol czar is an implementation of the Ashe protocol based on TCP multiplexing. Multiplexing involves reusing a single TCP connection for multiple Ashe protocols, which saves time on the TCP three-way handshake. However, this may result in a slight decrease in data transfer rate (approximately 0.19%). In most cases, using Protocol czar provides a better user experience compared to using the Ashe protocol directly.

$ daze server ... -p czar
$ daze client ... -p czar

Dahlia

Dahlia is a protocol used for encrypted port forwarding. Unlike many common port forwarding tools, it requires both a server and a client to be configured. Communication between the server and client is encrypted in order to bypass detection by firewalls.

# Port forwarding from 20002 to 20000:
$ daze server -l :20001 -e 127.0.0.1:20000 -p dahlia
$ daze client -l :20002 -s 127.0.0.1:20001 -p dahlia

Reminder again: Dahlia is not a proxy protocol but a port forwarding protocol.

Proxy Control

Proxy control is a rule that determines whether network requests (TCP and UDP) go directly to the destination or are forwarded to the daze server. Use the -f option in the daze client to adjust the proxy configuration.

• Use local network for all requests.
• Use remote server for all requests.
• Use both local and remote server (default).

File rule.ls

Daze uses a "rule.ls" file to customize your own rules(optional). "rule.ls" has the highest priority in routers so you should carefully maintain it. The "rule.ls" is located on the "./rule.ls" by default, or you can use daze client -r path/to/rule.ls to apply it.

L a.com
R b.com
B c.com

• L(ocale) means using local network
• R(emote) means using proxy
• B(anned) means to block it, often used to block ads

Glob is supported, such as R *.google.com.

File rule.cidr

Daze also uses a CIDR(Classless Inter-Domain Routing) file to route addresses. The CIDR file is located at "./rule.cidr", and has a lower priority than "rule.ls".

By default, daze has configured rule.cidr for China's mainland. You can update it manually via daze gen cn, this will pull the latest data from http://ftp.apnic.net/apnic/stats/apnic/delegated-apnic-latest.

DNS resolver

The DNS server and DNS protocol used by Daze can be specified through command line parameters.

• DNS: daze ... -dns 1.1.1.1:53
• DoT: daze ... -dns 1.1.1.1:853
• DoH: daze ... -dns https://1.1.1.1/dns-query

This article briefly describes the difference between them. I know many people don't like to read articles, so I just suggest that add -dns 1.1.1.1:853 in daze.