Hi there ~ 😇

Foreword There will never be a perfect camouflage. All protocols shares the risk of being identified. Common middlebox attack methods Passive analysis (traffic characteristics, PoC vulnerabilities) Often used to analyse plaintext traffic or TLS handshakes Active probing Generally deployed against Shadowsocks, V2Ray, TLS 1.3 (Getting server SSL certificates) Traffic replay attack Characteristics of proxy traffic Long connections Most HTTP traffic just loads and disconnects, hence long connections to an address can be an easy way to identify proxy traffic...

Creating an XrayR node To connect a server to an airport backend, we will be using XrayR, an open source and free backend for Xray protocols. If using TLS - assigning certificates Most of the time, we will be using Vmess over Websockets with TLS encryption as our protocol. This means that we will need a TLS certificate in order to secure our service. To do this, you will need to have:...

Sometimes universal clipboard can break. Here’s how to fix that. Manually enable clipboard sharing Open terminal Type in defaults write ~/Library/Preferences/com.apple.coreservices.useractivityd.plist ClipboardSharingEnabled 1 Restart your Mac.

Surfshark in China - October 2022 After quite a lot of thorough testing, I can finally come to the conclusion that Surfshark is working very well granted that its DNS servers are not poisoned, which is often the case behind the GFW in the Chinese internet. Fortunately, there are numerous ways that we can combat this issue. What’s working, what’s not Service Status Main website Working, but DNS poisoned Android App Fully working iOS App Login affected, connection affected Windows App Login affected, connection affected MacOS App Login affected, connection affected Linux App Fully working Manual configurations Partially working, “for China” config files mostly working DNS poisoning is the main culprit behind connection issues....

First, create a resource group: az group create --name <name> --location <location> Then, create the VM: az vm create \ --resource-group <name> \ --name <name> \ --image Debian \ --admin-user <username> \ --admin-password <password> \ --authentication-type password \ --os-disk-size-gb 64 \ --public-ip-address-allocation static \ --public-ip-sku Standard \ --size <server size>