viRikaRe
viRikaRe
Found this issue: docker/for-win#3171. Seems to be the fault by either WSL or Hyper-V that reserves too many port ranges. _TL;DR_ 1. Check if port 12546 is in excluded port...
可能是处理Shadowsocks的分流规则存在问题,所以仅当域名策略+预定义规则设置成需要分流时才会触发。具体表现: * 当域名策略为`AsIs`时,预定义规则可任选都没问题 * 当预定义规则为`全局`时,域名策略可任选都没问题 * 当域名策略为`IPIfNonMatch`或`IPOnDemand`且预定义规则为`绕过局域网地址而后代理`或`绕过大陆地址而后代理`时,Shadowsocks代理延迟测试在4000ms以上 * 当域名策略为`IPIfNonMatch`或`IPOnDemand`且预定义规则为`绕过局域网及大陆地址而后代理`时,Shadowsocks代理延迟测试失败 * 仅Shadowsocks协议存在此问题,VMess和VLESS没问题 * 版本: v1.7.38 (Lib v24, Xray-core v1.7.5),从Google Play安装
I just wonder what kind of MITM attacker will ever use this vulnerability. * When ISP/GFW doesn't suspect you, it shall not mess-up the connection. Otherwise it degrades the service...