feat(xray): update xray-core to v26.10.10 and adapt panel

Move the three Xray binary pins (DockerInit.sh, both release.yml
fetches) to v26.10.10, in lockstep with the xtls/xray-core module that
82c77111 already bumped to 701af60772cd.

xdns finalmask (#7090): a domain now takes a "names" list instead of a
single "name", and a resolver is an "addrs" list of udp:// or tcp://
URLs instead of {type, settings:{addr}}. The loader ignores the old
keys rather than failing, so every mask the 26.9.30 seeder wrote would
load with no domain and no resolver and the tunnel would carry nothing.
maskcompat.UpgradeLegacyXdns now lifts both the pre-26.9.30 string lists
and the 26.9.30 objects straight to names/addrs, dropping entries the
old loader refused. A new seeder (XdnsFinalmaskNamesAddrsFix) reruns it
over every stored finalmask, and the save path, GetXrayConfig, both
link importers and the mask editor's mount lift go through it. Template
outbounds now get the build-time heal too: a 26.9.30 template pasted
after the seeder passes the save check, since the core loads that shape
without error. The editor edits names and addrs as tag lists and no
longer requires record types, which the core now defaults (TXT on a
client, A/CNAME/TXT/AAAA on a server). The wire format did not change,
but clients on an older core cannot read the new config shape.

Lua scripts (#6823): dns.script, routing.script and dns servers[].id
are new. The xray page parsed the dns block with a strict schema, so
loading it dropped script and id and the next save deleted them; the
schema now keeps both and the DNS server modal carries the id through
an edit. The hot routing apply built routing in-process, and that build
now resolves the script file from the panel's working directory, so a
script beside the xray binary failed every rule change into a full
restart and broke the node bridge. RoutingService cannot change the
script anyway, so the panel no longer resolves it there.

TLS client roots (#7105): the core now verifies against its bundled
Mozilla roots instead of the OS store unless tlsSettings.useSystemCA is
set. The outbound TLS form gets a switch for it, so an outbound to a
server signed by a privately installed CA can opt back in.
This commit is contained in:
MHSanaei
2026-10-11 07:55:12 +02:00
parent 82c7711189
commit 73a028f52d
37 changed files with 553 additions and 205 deletions
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "اسم الخادم",
"verifyPeerName": "التحقق من اسم peer",
"pinnedSha256": "SHA256 مثبت",
"useSystemCA": "استخدام CA النظام",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "فاصل keep alive",
+1
View File
@@ -2047,6 +2047,7 @@
"serverNamePlaceholder": "server name",
"verifyPeerName": "Verify peer name",
"pinnedSha256": "Pinned SHA256",
"useSystemCA": "Use system CA",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "Keep alive interval",
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "nombre del servidor",
"verifyPeerName": "Verificar nombre del peer",
"pinnedSha256": "SHA256 pinned",
"useSystemCA": "Usar CA del sistema",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "Intervalo keep alive",
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "نام سرور",
"verifyPeerName": "تایید نام Peer",
"pinnedSha256": "SHA256 پین‌شده",
"useSystemCA": "استفاده از CA سیستم",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "بازه Keep alive",
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "nama server",
"verifyPeerName": "Verifikasi nama peer",
"pinnedSha256": "SHA256 pinned",
"useSystemCA": "Gunakan CA sistem",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "Interval keep alive",
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "サーバー名",
"verifyPeerName": "peer 名を検証",
"pinnedSha256": "Pinned SHA256",
"useSystemCA": "システムの CA を使用",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "keep alive 間隔",
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "nome do servidor",
"verifyPeerName": "Verificar nome do peer",
"pinnedSha256": "SHA256 pinned",
"useSystemCA": "Usar CA do sistema",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "Intervalo keep alive",
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "имя сервера",
"verifyPeerName": "Проверять имя peer",
"pinnedSha256": "Pinned SHA256",
"useSystemCA": "Использовать системные CA",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "Интервал keep alive",
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "sunucu adı",
"verifyPeerName": "Peer Adını Doğrula",
"pinnedSha256": "Sabitlenmiş SHA256",
"useSystemCA": "Sistem CA'sını kullan",
"shortId": "Kısa Kimlik",
"sockopts": "Sockopts",
"keepAliveInterval": "Keep Alive Aralığı",
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "ім'я сервера",
"verifyPeerName": "Перевіряти ім'я peer",
"pinnedSha256": "Pinned SHA256",
"useSystemCA": "Використовувати системні CA",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "Інтервал keep alive",
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "tên máy chủ",
"verifyPeerName": "Xác minh tên peer",
"pinnedSha256": "SHA256 pinned",
"useSystemCA": "Dùng CA của hệ thống",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "Khoảng keep alive",
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "服务器名",
"verifyPeerName": "验证 peer 名称",
"pinnedSha256": "Pinned SHA256",
"useSystemCA": "使用系统 CA",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "keep alive 间隔",
+1
View File
@@ -1929,6 +1929,7 @@
"serverNamePlaceholder": "伺服器名稱",
"verifyPeerName": "驗證 peer 名稱",
"pinnedSha256": "Pinned SHA256",
"useSystemCA": "使用系統 CA",
"shortId": "Short ID",
"sockopts": "Sockopts",
"keepAliveInterval": "keep alive 間隔",