Xray-core: tls: bad record MAC
完整性要求
- 我保证阅读了文档,了解所有我编写的配置文件项的含义,而不是大量堆砌看似有用的选项或默认值。
- 我搜索了issues,没有发现已提出的类似问题。
版本
1.8.11
描述
client -> server1 -(vless+tcp+reality)-> server2 -(vless+tcp+reality)-> server3
server1 xray 1.8.11 (normal) outbound1(vless+tcp+reality[to server3])->streamSettings(“dialerProxy”: “outbound2”,) outbound2(vless+tcp+reality[to server2])
server2 xray 1.8.11 (normal)
server3 xray 1.8.11 (error) app/proxyman/inbound: connection ends > proxy/vless/inbound: connection ends > proxy/vless/inbound: failed to transfer request payload > local error: tls: bad record MAC
重现方式
server1 - outbound
{
"tag": "out-server3",
"protocol": "vless",
"settings": {
"vnext": [
{
"address": "server3",
"port": 443,
"users": [
......
]
}
]
},
"streamSettings": {
"network": "tcp",
"security": "reality",
"realitySettings": {
......
},
"sockopt": {
"dialerProxy": "out-server2",
"mark": 255
}
}
},
{
"tag": "out-server2",
"protocol": "vless",
"settings": {
"vnext": [
{
"address": "server2",
"port": 443,
"users": [
......
]
}
]
},
"streamSettings": {
"network": "tcp",
"security": "reality",
"realitySettings": {
......
},
"sockopt": {
"mark": 255
}
}
},
===============================
server2 -
inbound: {
"tag": "in-reality",
"protocol": "vless",
"port": 443,
"settings": {
"clients": [
......
],
"decryption": "none"
},
"streamSettings": {
"network": "tcp",
"security": "reality",
"realitySettings": {
......
}
}
},
outbound : freedom
===============================
server3 - inbound
{
"tag": "in-reality",
"protocol": "vless",
"port": 443,
"settings": {
"clients": [
......
],
"decryption": "none"
},
"streamSettings": {
"network": "tcp",
"security": "reality",
"realitySettings": {
......
}
}
},
日志
server3 出現 error tls: bad record MAC
app/proxyman/inbound: connection ends > proxy/vless/inbound: connection ends > proxy/vless/inbound: failed to transfer request payload > local error: tls: bad record MAC
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 17 (8 by maintainers)
收到, 我会再留意情况, 谢谢
=====
原问题 client -> server1 -(vless+tcp+reality)-> server2 -(vless+tcp+reality)-> server3
补充 : client -(http/tproxy)-> server1 -(vless+tcp+reality)-> server2 -(vless+tcp+reality)-> server3
client : 有 android, ios, windows, ubuntu server1 : 有 Debian 12, ubuntu 22.04 server2 : ubuntu 22.04 server3 : ubuntu 22.04
=====
修改 client -(http/tproxy)-> server1 -(vless+tcp+reality)-> server2 -(vless+tls+grpc)-> server3
如修改 由: server2 -(vless+tcp+reality)-> server3 到: server2 -(vless+tls+grpc)-> server3
tls: bad record MAC 就不会再出现
=====
1.8.13 tls: bad record MAC 问题还存在, 但只会在一些情况出现, 但要详细测试才可给出 出现场景
测试最新1.8.13版本已无此问题。
对性能来说是这样,对“不想让观察者关联两个或多个连接”来说不合适,所以还是不适合 tor,
虽然它就多加密几层还是能被关联对于“不想让观察者关联两个或多个连接”的起夜级需求,我想了下还是只能空跑流量抹平时序特征,like https://github.com/v2ray/v2ray-core/issues/2526#issuecomment-783931231 ,
比 hysteria 的 brutal 更激进,不过这样的强特征又不适合过墙了,有点难取舍,好在我没有搞回国流量 ghs 的需求