# SpoofDPI

Read in other Languages: [English](https://github.com/xvzc/SpoofDPI), [한국어](https://github.com/xvzc/SpoofDPI/blob/main/readme_ko.md)

A simple and fast software designed to bypass **Deep Packet Inspection**  
  
![image](https://user-images.githubusercontent.com/45588457/148035986-8b0076cc-fefb-48a1-9939-a8d9ab1d6322.png)


# 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
> If you are using any vpn extensions such as Hotspot Shield in Chrome browser,   
  go to Settings > Extensions, and disable them.
### 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](https://github.com/ValdikSS/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](https://github.com/SadeghHayeri/GreenTunnel) by @SadeghHayeri  
[GoodbyeDPI](https://github.com/ValdikSS/GoodbyeDPI) by @ValdikSS