Recent pull requests left the "Submitted and answered for by" line
filled in by an assistant or dropped, kept a commit that a later
commit reverted, and described changes their diff no longer had.
CONTRIBUTING.md also told contributors to run "the checks CI runs",
but CI runs neither go vet nor go test, and it named Go 1.26 while
core/ needs 1.27.
- CONTRIBUTING.md: Go 1.27; say which checks CI runs; squash a commit that undoes part of an earlier one; a bug fix
comes with a failing test or a reproduced failure; check the title,
description and messages against the diff; the sign-off line and the
boxes are the contributor's.
- AGENTS.md: ask before changing behaviour that may be intentional; a
check that ran nothing proves nothing; leave the sign-off line and
the human's boxes alone.
- Pull request templates: the sign-off line is required and written by
the contributor.
v2raya.org is parked and redirects to spam and malware pages (#2109).
The GUI still sent users there: the mixed-content banner offered a
"switch to alternate site" button that opened http://v.v2raya.org, and
gui/public/CNAME shipped in every build.
The banner now tells the user to open the GUI over http at the
service's own address instead, the CNAME is gone, and the About page
links the project website, daeuniverse.org.
Closes#2109
runtimeAssetDir called os.MkdirAll on $XDG_RUNTIME_DIR/v2raya with mode
0700. When v2rayA runs as root on a system where /run/user does not
exist yet (OpenRC with elogind before any login), that created
/run/user itself as 0700 root:root, and every other user then failed to
get a runtime directory.
The runtime directory belongs to the login manager, so use it only when
it already exists and otherwise put the asset links in the
configuration directory, as a service user without a session already
does. A regular file there is one the user placed, so the lookup now
uses it instead of replacing it with a link to the system copy.
Closes#2092
A VLESS link with security=tls carries its ECH config list in the ech
query parameter. The service dropped it on import, so the stored node,
the generated core config and the exported share link all lost it, and
the server editor dropped it again when a node was edited and saved.
Parse ech into the stored node, pass it to the core as the TLS
settings' echConfigList, and write it back to share links when the
node uses TLS, in the service and in the editor's codec. The service
reads ech from the raw query so that an unescaped "+" in the base64
list stays a "+" instead of becoming a space. The VLESS
encryption half of the original change landed in 3e374af9.
Closes#2093
With about 1,400 nodes the proxies page froze for a minute on every
visit: it mounted a card, a menu and a tooltip for every row at once,
and each render looked group membership and selection up with a linear
scan per row. The source filter also went back to "all" every time, so
the user waited for the full list before they could narrow it.
The page now mounts 60 rows and adds the next 60 as a sentinel below
the last row scrolls into view; a new search, source or view starts
again from the first page. Select-all, Ctrl+A, the latency test and the
batch actions still work on the whole filtered list. Membership is
indexed once per member list, so inGroup is a map lookup, each row
keeps the same groups array between renders, and selection is checked
against a set; batch add and remove no longer compare every pair.
The selected source is stored like the view. Before the first sync
only "all" and "local" exist, so a saved subscription source is
dropped only after the subscriptions have loaded and it is not among
them.
Closes#2105
TUN mode runs `ip -4 route add default dev tun0 table 2020` and the
matching `ip rule` commands. The image is Alpine, whose busybox `ip`
rejects a numeric table ID ("ip: invalid argument '2020' to 'table'"),
so TUN mode could not start in the official container. iproute2
provides an `ip` that accepts it.
Closes#2077
_install_zig.yml was declared as a reusable workflow but called from a
step, and a step-level uses only accepts an action, so the workflows
failed to validate. A job-level workflow call cannot help here either,
because Zig has to be on PATH in the same job as the build.
Move the install into .github/actions/install-zig, which pins the Zig
version itself and keeps both call sites on a single step.
Auto mode previously trusted the iptables userspace backend alone. On PREEMPT_RT kernels, legacy xtables is unavailable even when the legacy iptables binary is installed. Probe the mangle table read-only and select nft only for the specific missing-table failure. Add regression coverage for backend detection and conservative error handling.
The release page now carries installer_alpine_<arch>_<version>.apk. It is
built without a key from Alpine's trust store, so apk needs
--allow-untrusted.
The fpm invocation and its four hand-written architecture tables give way
to nfpm driven by install/nfpm/v2raya.yaml: nfpm maps the Go architecture
onto the name each packager expects, and writes the packages straight to
their published file names, so the rename step goes away too.
The package file names and the architecture matrix stay as they were, and
an apk package is added for Alpine, which boots the OpenRC script instead
of a systemd unit.
after_install.sh and after_upgrade.sh were the fpm hooks; their only
caller is gone, and the nfpm config carries equivalent maintainer
scripts.
install/nfpm/v2raya.yaml describes every Linux package of a release: the
two binaries, the rule data the packaging job downloads, the desktop
entry, nine icon sizes rendered from gui/src/assets/img/v2raya-icon.svg,
and, per packager, either the systemd units or the OpenRC init script
together with its conf.d file.
The rule data is shipped as regular files rather than as symlinks into a
v2ray-rules-dat package, which no distribution provides.
The maintainer scripts reload systemd where it exists and do nothing on
Alpine.
Xray v26.10.31 rejects VLESS with encryption none and no TLS or REALITY on public addresses, so post-quantum encryption strings must reach the core. Parse, generate and export the vless encryption and pqv share-link parameters, and expose both in the server editor with translations for all locales.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Update the dependency and its transitive modules. Xray moved PacketConnWrapper from transport/internet to common/net, so refresh the references in the TUIC and Juicity outbound comments.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
deleteTransparentProxyRules returned before touching the system proxy
whenever no snapshot had been persisted. GetCleanCommands already
handles both cases -- it restores the saved original when a snapshot
exists and falls back to disabling ProxyEnable when none does -- so the
guard only suppressed the fallback that makes the two modes exclusive.
The leftover registry value pointed at 52345, which only the
system_proxy mode ever listens on. Switching back to tun therefore left
proxy-using applications connected to a dead port: their sockets stayed
in SYN_SENT until the process was restarted.
The regression test drives deleteTransparentProxyRules with no snapshot
and asserts the proxy is disabled. Against the previous code it fails
with "the system proxy was never touched"; it passes with this change.