From 481aa13b502464b07af966fd7d05b01a03726b7f Mon Sep 17 00:00:00 2001 From: Kc2353 <130827856+Kc2353@users.noreply.github.com> Date: Fri, 12 Jun 2026 12:14:14 +0800 Subject: [PATCH 1/3] Update Encryption section in vless.md --- docs/development/protocols/vless.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/development/protocols/vless.md b/docs/development/protocols/vless.md index c5297cb420..902371a0a6 100644 --- a/docs/development/protocols/vless.md +++ b/docs/development/protocols/vless.md @@ -60,6 +60,7 @@ Schedulers 没必要像下面的 Encryption 一样整个套在外面，因为头 BETA 2 预计推出两个初级的 Scheduler：Zstd 压缩、数据量动态扩充。进阶操作才是从宏观层面来控制、分配，暂时咕咕。 ## Encryption +目前实现见 [VLESS Encryption](https://github.com/XTLS/Xray-core/pull/5067) 与 VMess 的高度耦合不同，VLESS 的服务端、客户端不久后可以提前约定好加密方式，仅在外面套一层加密。这有点类似于使用 TLS，不影响承载的任何数据，也可以理解成底层就是从 TLS 换成预设约定加密。相对于高度耦合，这种方式更合理且灵活：一种加密方式出了安全性问题，直接扔掉并换用其它的就行了，十分方便。VLESS 服务端还会允许不同的加密方式共存。 From 3f62bfd6b321c2ba12b7c8c8e9497b1ab03d3c2e Mon Sep 17 00:00:00 2001 From: Kc2353 <130827856+Kc2353@users.noreply.github.com> Date: Fri, 12 Jun 2026 12:18:55 +0800 Subject: [PATCH 2/3] Update Encryption section in vless.md --- docs/en/development/protocols/vless.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/en/development/protocols/vless.md b/docs/en/development/protocols/vless.md index 66da5fbdbc..6a926587f8 100644 --- a/docs/en/development/protocols/vless.md +++ b/docs/en/development/protocols/vless.md @@ -60,6 +60,8 @@ Schedulers don't need to wrap everything on the outside like Encryption below, b BETA 2 is expected to launch two elementary Schedulers: Zstd compression and dynamic data expansion. Advanced operations involve controlling and allocating from a macro level, which is postponed for now. ## Encryption + + See [VLESS Encryption](https://github.com/XTLS/Xray-core/pull/5067). Unlike VMess's high coupling, VLESS servers and clients will soon be able to agree on an encryption method in advance, wrapping only one layer of encryption on the outside. This is somewhat similar to using TLS; it doesn't affect any carried data and can be understood as swapping the underlying layer from TLS to a preset agreed encryption. Compared to high coupling, this method is more reasonable and flexible: if a security issue arises with one encryption method, just discard it and switch to another, very convenient. VLESS servers will also allow different encryption methods to coexist. From 927afe913f3f23e311f969f15d938c6fa62e912a Mon Sep 17 00:00:00 2001 From: Kc2353 <130827856+Kc2353@users.noreply.github.com> Date: Fri, 12 Jun 2026 12:19:17 +0800 Subject: [PATCH 3/3] Update Encryption section in vless.md minor mistake --- docs/development/protocols/vless.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/development/protocols/vless.md b/docs/development/protocols/vless.md index 902371a0a6..6011ce4383 100644 --- a/docs/development/protocols/vless.md +++ b/docs/development/protocols/vless.md @@ -60,6 +60,7 @@ Schedulers 没必要像下面的 Encryption 一样整个套在外面，因为头 BETA 2 预计推出两个初级的 Scheduler：Zstd 压缩、数据量动态扩充。进阶操作才是从宏观层面来控制、分配，暂时咕咕。 ## Encryption + 目前实现见 [VLESS Encryption](https://github.com/XTLS/Xray-core/pull/5067) 与 VMess 的高度耦合不同，VLESS 的服务端、客户端不久后可以提前约定好加密方式，仅在外面套一层加密。这有点类似于使用 TLS，不影响承载的任何数据，也可以理解成底层就是从 TLS 换成预设约定加密。相对于高度耦合，这种方式更合理且灵活：一种加密方式出了安全性问题，直接扔掉并换用其它的就行了，十分方便。VLESS 服务端还会允许不同的加密方式共存。