sing-box Fork Expands from Desktop VPN Launcher to Android and Router Deployments
The sing-box-lx project, an actively maintained fork of sing-box, has completed its transition from a desktop VPN engine to a unified platform running on Android devices and OpenWrt routers. The developer behind L×Box and Sing-box Launcher reports more than 1,700 commits, 24 stable 1.14 releases, and roughly seventy specialized builds since June.
Two major protocol additions stand out. A native MASQUE outbound implements CONNECT-IP as defined in RFC 9484, tunneling complete IP packets rather than UDP datagrams and reusing the same userspace network stack employed by WireGuard endpoints. The implementation treats Cloudflare WARP as a configuration preset while keeping device registration outside the core. AmneziaWG 2.0 received exhaustive verification against amneziawg-tools, the upstream kernel module netlink interface, and live IPC round-trips, confirming parity on all sixteen obfuscation parameters including Jc/Jmin/Jmax junk packets, S1–S4 padding, H1–H4 magic headers, and I1–I5 signature packets.
Android required extensive runtime optimizations. A full state machine now suspends idle WireGuard and AmneziaWG endpoints, sometimes destroying userspace devices entirely, and restores them lazily on first use. Health checks skip cycles when recent traffic has succeeded. The resulting savings reach 31 percent lower resident set size and 80 percent lower kernel CPU usage on production configurations. Additional fixes eliminated 127-second TCP dial timeouts caused by unbounded gVisor SYN backoff and ensured prompt recovery after Android Doze cycles.
Several long-standing silent failures were resolved during the summer. A three-byte change restored REALITY compatibility after Xray 26.7.11 began enforcing minimum client versions. XHTTP path handling now correctly appends trailing slashes, and mutual uplink/downlink deadlock in packet-up scenarios was eliminated. XMUX connection reuse and automatic TLS record fragmentation for detoured outbounds were also added.
The newest component, sing-box lxd, is a headless daemon that hosts the core and exposes a persistent gRPC management channel. Designed for routers, it survives configuration reloads, validates candidates before apply, performs automatic rollback on failure, and delivers the same structured observability previously available only to Android clients. An additional REST endpoint aggregates DHCP leases, ARP tables, bridge FDB entries, hostapd data, and operator labels to map IP addresses to human-readable device names.
Releases continue to follow three self-imposed rules: drift from upstream is measured by merge-base rather than commit count, every submodule is integrity-checked before merge, and no stable tag is cut without execution on real hardware. Static musl binaries for router architectures, including big-endian MIPS, are published alongside detailed OpenWrt recipes for isolated VPN SSIDs.
Related articles
Google Testing Optional Google Account Unlock for Forgotten Android PINs
Google is developing a backup unlock method that lets Android users regain access to their devices through a linked Google Account instead of performing a full factory reset. The feature, discovered in Android 17 QPR2 Beta 5, appears under the name Unlock with Google Account and would be disabled by default. Users would need to enable it manually in the Device unlock settings before forgetting their PIN, password, or pattern. The change aims to prevent permanent loss of local data such as photos and documents that lack cloud backups. The mechanism revives a capability removed after Android 4.4, when forgotten patterns could be cleared using Google Account credentials. Factory Reset Protection would remain in place after any reset. The code reference is not yet functional, carries no official announcement, and may be altered or dropped before release.
Implementing 2FA Kubernetes Access via Gateway API, Dex and MULTIDIRECTORY
A Russian cybersecurity company replaced static kubeconfig files with corporate accounts and mandatory 2FA for its Talos Linux Kubernetes clusters. The solution routes all authentication through a single FQDN using NGINX Gateway Fabric, Dex as an OIDC provider connected to MULTIDIRECTORY via LDAP, and kube-oidc-proxy for token validation and impersonation. Groups stored in the directory are passed directly into RBAC bindings, eliminating manual certificate management. A lightweight Python service dynamically generates kubeconfig files that contain no secrets. The team documented several Gateway API migration pitfalls including namespace route restrictions and BackendTLSPolicy hostname validation. The approach keeps the entire configuration in Git and avoids modifying kube-apiserver flags.
Windows File System Tunneling Preserves Old File Metadata for Legacy Compatibility
Microsoft has clarified that Windows sometimes assigns creation dates from deleted files to new ones due to a long-standing mechanism called File System Tunneling. The feature keeps metadata in a short-term cache for about 15 seconds after a file is deleted or renamed. If a new file with the same name is created quickly in the same folder, it inherits the previous file's timestamps and short-to-long name mappings. This behavior exists to support safe saving patterns used by many applications and to maintain compatibility with old DOS-era 8.3 filename formats. The actual file content is never restored, only the metadata. The cache is temporary and clears over time, so the effect does not occur with files deleted long ago. The explanation came after users noticed unexpected dates in Windows Explorer and questioned whether it was a bug.
Amazon Confirms Irrecoverable Data Loss in UAE and Bahrain Data Centers After Drone Attacks
Amazon Web Services has officially confirmed that data stored in specific availability zones within its Middle East regions was permanently destroyed following physical attacks on data centers in the UAE and Bahrain. The incidents began on March 1 and continued through April and July, damaging infrastructure tied to AI development projects. In the UAE region mec1, only zone mec1-az2 was completely destroyed with no external backups, while mec1-az3 suffered severe damage and mec1-az1 remained operational but overloaded. All three zones in the Bahrain region me-south-1 were rendered inoperable. AWS had spent six months attempting recovery before issuing the final statement on September 15, 2026, and has advised customers to migrate workloads to unaffected regions. The event highlights growing risks to data from physical-world attacks beyond traditional network threats.