mirrors/SpoofDPI
1
0
Fork 0
mirror of https://github.com/xvzc/SpoofDPI.git synced 2024-12-22 14:26:31 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

README.md: Fix typos (#206)

Browse Source
This commit is contained in:
Christian Clauss 2024-08-27 10:24:56 +02:00 committed by GitHub
parent 0699e50d15
commit efa64ab4c0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -55,13 +55,13 @@ google-chrome --proxy-server="http://127.0.0.1:8080"
# How it works # How it works
### HTTP ### 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. Since most websites in the world now support HTTPS, SpoofDPI doesn't bypass Deep Packet Inspections for HTTP requests, However, it still serves proxy connection for all HTTP requests.
### HTTPS ### HTTPS
Although TLS encrypts every handshake process, the domain names are still shown as plaintext in the Client hello packet. Although TLS 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. 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. The domain name can offer 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. 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 split into chunks.
What SpoofDPI does to bypass this is to send the first 1 byte of a request to the server, What SpoofDPI does to bypass this is to send the first 1 byte of a request to the server,
and then send the rest. and then send the rest.