GeorgeXie2333/usque-app v0.2.7

on GitHub

• VPN Gate embeds an OpenVPN TCP session carried by the private WARP dialer, without a second OS VPN interface or an external OpenVPN process. The final tunnel supplies addresses, DNS and MTU; unsupported proxied IPv6 is blocked. One internal startup authentication retry reuses the same saved node only after the rejected worker stops. Cancellation closes admission, and an unconfirmed bounded stop remains pending rather than being reported as complete.
  
  VPN Gate 内嵌由私有 WARP 拨号器承载的 OpenVPN TCP 会话，不创建第二个系统 VPN 接口或外部 OpenVPN 进程。地址、DNS 与 MTU 来自最终隧道；不支持的代理 IPv6 会被阻止。启动认证仅内部重试一次，并且必须在被拒绝的工作线程停止后才复用同一已保存节点。取消会关闭流量准入，有界停止未确认时仍记为待完成，不冒充停止成功。
• The cumulative directory validates pinned snapshots and configuration hashes before use. Local favorites, saved selections, drafts and in-flight preparations retain independent references. Refresh failures or disappearing nodes do not silently replace saved configurations. Traffic samples describe the final Gate channel, while RTT, loss and congestion observations describe the WARP underlay, not the full volunteer-exit path.
  
  累积目录在使用前验证固定快照和配置哈希。本地收藏、已保存选择、草稿与进行中的配置准备分别持有独立引用。刷新失败或节点消失不会静默替换已保存配置。流量采样描述最终 Gate 通道，而 RTT、丢包与拥塞观测描述 WARP 底层连接，并非经过志愿出口的完整路径。
• Windows separates application-lifetime device leases from connection packet leases, joins packet waiters before replacement, and rejects stale ownership and generation results. Recovery journal schema 3 conservatively reads schema 2; failed retirement-record writes retry without repeating native deletion or restarting the connection recovery budget. Configuration schema stays at 15, Agent protocol is 3, and sanitized recovery exports remain schema 2. Sensitive identity and configuration data are excluded from diagnostic exports.
  
  Windows 将应用生命周期设备租约与连接数据包租约分离，在替换前等待数据包等待线程结束，并拒绝过期所有权及代次结果。恢复日志 schema 3 保守读取 schema 2；设备退役记录写入失败会重试，但不会重复原生删除或重置连接恢复预算。配置 schema 保持 15，Agent 协议为 3，脱敏恢复导出仍为 schema 2。诊断导出排除敏感身份与配置数据。
• Android restores status subscriptions after resume, binds exit probes to the final tunnel, and coordinates interface handoff and terminal cleanup. Ending a failed VPN restores ordinary network access outside Android Lockdown; in-process traffic admission is not an independent OS Kill Switch. UI changes improve proxy status cards, country filtering, local proxy controls, validation priority and appearance-picker accessibility.
  
  Android 在恢复后重新订阅状态，将出口探测绑定至最终隧道，并协调接口交接与终止清理。在 Android Lockdown 之外，结束失败的 VPN 会恢复普通网络访问；进程内流量准入不等于独立的系统 Kill Switch。界面改进涵盖代理状态卡、国家筛选、本地代理控制、验证反馈优先级和外观选择器无障碍标签。
• The multilingual Windows EXE installers introduced in v0.2.6 remain the user-facing packages; signed MSIs remain reserved for verified in-app updates. The newer-Agent-first upgrade bridge introduced in v0.2.5 remains in place for v0.2.4 upgrades. Dependency maintenance includes reviewed Rust, Flutter, Kotlin and Actions updates, with locked native source and license inventories included in release SBOMs. No measured performance improvement or real-machine upgrade result is claimed.
  
  v0.2.6 引入的多语言 Windows EXE 安装程序仍为用户安装入口；签名 MSI 仍仅供经过验证的应用内更新。v0.2.5 引入的新版 Agent 优先安装机制继续为 v0.2.4 升级提供兼容桥接。依赖维护包含经审查的 Rust、Flutter、Kotlin 和 Actions 更新，发布 SBOM 纳入锁定的原生源码与许可证清单。不宣称已测得性能提升或已完成真实机器升级验证。

DNS privacy / DNS 隐私

GeoSite-matched direct-country queries use the selected direct DNS mode. System (the default) exposes them to the physical DNS provider; DoH or DoT exposes them to the configured encrypted resolver using numeric bootstrap and strict TLS, with no plaintext fallback. Other remote queries use the final tunnel's DNS: WARP normally, or VPN Gate when enabled. Explicit local/direct DNS choices remain in effect. Apps using their own encrypted DNS hide domains from Usque, so routing falls back to GeoIP classification.

与 GeoSite 匹配的直连国家规则查询会使用所选直连 DNS 模式。System（默认）会将查询暴露给物理 DNS 提供商；DoH 或 DoT 使用数字 IP 引导和严格 TLS，将查询发送给配置的加密解析器，且不回退至明文。其他远端查询使用最终隧道的 DNS：通常为 WARP，启用 VPN Gate 后则为 VPN Gate。显式本地或直连 DNS 选择仍然生效。应用自行使用加密 DNS 时，Usque 无法获知域名，路由会回退至 GeoIP 分类。

VPN Gate directory services learn directory requests, the WARP provider carries the OpenVPN connection, and the selected volunteer provides final egress and can observe traffic leaving that tunnel subject to application encryption. Existing Geo, CIDR, LAN, system-proxy bypass and Android application exceptions retain their direct behavior. Public node scores and TCP observations are not local end-to-end measurements or promises of availability. No automatic telemetry or diagnostic upload is added. See the VPN Gate guide for the complete boundaries.

VPN Gate 目录服务可见目录请求，WARP 提供商承载 OpenVPN 连接，所选志愿节点提供最终出口，并可在应用加密的边界内观察离开该隧道的流量。已有 Geo、CIDR、LAN、系统代理绕过及 Android 应用例外保留直连行为。公共节点评分与 TCP 观测不是本地端到端测量，也不保证可用性。不新增自动遥测或诊断上传。完整边界请参阅 VPN Gate 指南。

Without VPN Gate, experimental L4 remains TCP-only: valid tunneled UDP/53 queries are converted to TCP DNS and preserve the application-selected resolver IP. EdgeResolved for L4 SOCKS5/HTTP sends hostnames to the CONNECT edge without a local lookup; it cannot recover names from TUN IP traffic. VPN Gate can carry business UDP as IP packets inside its OpenVPN TCP channel. Neither mode silently converts failed proxied traffic into direct traffic.

未启用 VPN Gate 时，实验性 L4 仍仅支持 TCP：有效的隧道 UDP/53 查询转换为 TCP DNS，并保留应用指定的解析器 IP。L4 SOCKS5/HTTP 的 EdgeResolved 会将域名发送至 CONNECT 边缘节点而不进行本地查询，不能从 TUN IP 流量还原域名。VPN Gate 可将业务 UDP 作为 IP 数据包承载于其 OpenVPN TCP 通道。两种模式都不会静默将失败的代理流量转为直连。