You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello
One of good features of Hysteria1 was it's obfuscations like Wechat-Video or FakeTCP that is not present at Hysteria2
We are still waiting for FakeTCP, but instead of Wechat-Video or DNS Header #587 \
You can add Header to Salamander, for example to fake a DNS Connection client can send [Fake DNS Request][Proxy Data] and server accept it like Hysteria1 was accepting Fake ALPN (by hardcoding the fake client request header to server)
And you can even set a fake response header at server side and hardcode it or it's bytes length at client side to make the fake connection even more real (Of course Fake DNS is easy for GFW to detect, but other protocols can be faked better)
And if you later added FakeTCP, you can add same feature to it, so users be able to Fake TCP Protocols too
The text was updated successfully, but these errors were encountered:
If you let user to add fake bytes as a Hex Stream
For adding random data between the header bytes, user can change random bytes to x and client change x to random hex character
For example for random DNS Transaction ID : xxxx0100000100000000000007737570706f7274076d6f7a696c6c61036f72670000010001
but it's longer than base64
Hello
One of good features of Hysteria1 was it's obfuscations like Wechat-Video or FakeTCP that is not present at Hysteria2
We are still waiting for FakeTCP, but instead of Wechat-Video or DNS Header #587 \
You can add Header to Salamander, for example to fake a DNS Connection client can send
[Fake DNS Request][Proxy Data]
and server accept it like Hysteria1 was accepting Fake ALPN (by hardcoding the fake client request header to server)And you can even set a fake response header at server side and hardcode it or it's bytes length at client side to make the fake connection even more real (Of course Fake DNS is easy for GFW to detect, but other protocols can be faked better)
And if you later added FakeTCP, you can add same feature to it, so users be able to Fake TCP Protocols too
The text was updated successfully, but these errors were encountered: