cloaky test (cbeuw/Cloak + sniproxy)

cloaky test (cbeuw Cloak + sniproxy)

$ cat cloaky_server.json
{
  "ProxyBook": {
    "sniproxy": [
      "tcp",
      "127.0.0.1:443"
    ]
  },
  "BindAddr": [
    "===server lan ip=========:443"
  ],
  "BypassUID": [
    "=======uid======="
  ],
  "RedirAddr": "cn.bing.com",
  "PrivateKey": "============priv key============="
}

# Andrew Ayer sniproxy, or ziozzang/SimpleSNIProxy
$ sudo ./sniproxy -l 127.0.0.1:443
$ sudo ./cloaky -c cloaky_server.json

$ cat cloaky_client.json
{
  "Transport": "direct",
  "ProxyMethod": "sniproxy",
  "EncryptionMethod": "chacha20-poly1305",
  "UID": "======ui===========",
  "PublicKey": "=========pub key=========",
  "ServerName": "cn.bing.com",
  "NumConn": 1,
  "BrowserSig": "firefox",
  "StreamTimeout": 300
}

$ sudo ./cloaky_client -c cloaky_client.json -l 443 -s <server wan ip>

$ curl -v --resolve myip.ipip.net:443:127.0.0.1 https://myip.ipip.net/

after 20 times requests, the <server wan ip>:443 has been blocked by GFW

mainly because that there's no http2 conection multiplex, only http1.3 Websocket multiplex.

=====================================================
Maybe "cloak + naiveproxy client(no cert verification) + HAProxy + naiveproxy forward" can avoid buying domain name.

it is difficult for me to modify naiveproxy client and naiveproxy server to realize cloak function:
https://github.com/klzgrad/naiveproxy/issues/312

So auto-getting a freenom is more realistic, but 8.8.4.4 or letsencrypt stabaly-cache the bare domain will take more than 1 hour