A simple and fast anti-censorship tool written in Go
Go to file
2022-01-08 02:03:46 +09:00
cmd/spoof-dpi remove SIGCONT 2022-01-07 17:55:37 +09:00
config refactor 2022-01-08 02:03:46 +09:00
proxy refactor 2022-01-08 02:03:46 +09:00
util refactor 2022-01-08 02:03:46 +09:00
.gitignore update .gitignore 2022-01-07 20:34:04 +09:00
go.mod update 2022-01-04 00:13:42 +09:00
go.sum update 2022-01-04 00:13:42 +09:00
LICENSE add license 2022-01-04 22:07:01 +09:00
readme_ko.md update readme 2022-01-04 22:08:44 +09:00
readme.md update readme 2022-01-04 22:10:09 +09:00
release add +x to release 2022-01-07 17:59:27 +09:00

SpoofDPI

Read in other Languages: English, 한국어

A simple and fast software designed to bypass Deep Packet Inspection

image

Dependencies

  • Go

Installation

  • With go install
    $ go install github.com/xvzc/SpoofDPI/cmd/spoof-dpi

    Remember that $GOPATH variable should be set in your $PATH

  • Or you can build your own
    $ git clone https://github.com/xvzc/SpoofDPI.git
    $ cd SpoofDPI
    $ go build ./cmd/...

Run

OSX

Run $ spoof-dpi

Linux

Run $ spoof-dpi and open your favorite browser with proxy option
google-chrome --proxy-server="http://127.0.0.1:8080"

Windows

Use GoodbyeDPI instead. It's way better

Usage

Usage: spoof-dpi [options...]
-dns=<addr>  | default: 8.8.8.8
-port=<port> | default: 8080

How it works

HTTP

Since most of websites in the world now support HTTPS, SpoofDPI doesn't bypass Deep Packet Inspections for HTTP requets, However It still serves proxy connection for all HTTP requests.

HTTPS

Although TLS 1.3 encrypts every handshake process, the domain names are still shown as plaintext in the Client hello packet. In other words, when someone else looks on the packet, they can easily guess where the packet is headed to. The domain name can offer a significant information while DPI is being processed, and we can actually see that the connection is blocked right after sending Client hello packet. I had tried some ways to bypass this, and found out that it seemed like only the first chunk gets inspected when we send the Client hello packet splited in chunks. What SpoofDPI does to bypass this is to send the first 1 byte of a request to the server, and then send the rest.

SpoofDPI doesn't decrypt your HTTPS requests, and that's why we don't need the SSL certificates.

Inspirations

Green Tunnel
GoodbyeDPI