Android 17 Adds Local Network Protection and Strengthens Wi-Fi Privacy Controls
Android 17 introduces new privacy protections designed to limit unauthorized tracking of users on Wi-Fi networks and restrict applications from accessing other devices connected to the same local network.
The key addition is Local Network Protection, which forces apps to request explicit user permission before they can scan for or connect to devices such as TVs, cameras, game consoles, printers and other equipment on the home Wi-Fi network. Previously, such scans could reveal the types of devices present in a household and help build detailed profiles of residents' habits and characteristics.
The restriction reduces this exposure while still allowing common legitimate functions, including casting video to a television.
The platform also adds default support for Encrypted Client Hello (ECH). This technology conceals the requested domain name during the initial phase of HTTPS connections, making it significantly harder for internet service providers, Wi-Fi operators or other third parties to identify which websites and services are being accessed.
Another change is the default activation of Certificate Transparency, a mechanism that requires public logging of digital certificates. The measure helps detect fraudulent or improperly issued certificates that could be used to intercept encrypted traffic.
Android 17 further expands protection against attacks that force smartphones to downgrade to insecure 2G networks. Attackers can deploy rogue base stations to downgrade 4G or 5G connections and deliver fraudulent messages directly to devices.
Related articles
New Obfuscation Method Dissolves Personal Data Records in Layer of Plausible Variants
A Russian information security researcher has proposed a data protection technique that renders stolen personal records unusable even after full compromise. The approach mixes real data such as phone numbers, emails, passports, addresses, INN and SNILS with vast numbers of semantically valid alternatives. Attackers receive nearly complete information including a 361-character message containing PIN codes and word order, yet lack the secret vector space and reconstruction algorithm required to identify the correct record. Without these components, brute-force attempts produce millions of plausible results with no architectural method to verify accuracy. The method is presented as an alternative to traditional encryption when data must remain accessible yet protected against extraction. A public sandbox is available for testing the approach.
Hydrat Project Builds Automated WireGuard Gateway for Resilient VLESS and Tor Routing
A developer has released Hydrat, a self-hosted gateway that connects devices via WireGuard while automatically managing VLESS and Tor backends to survive server blocks and quality degradation. The system maintains a pool of tested proxies, performs continuous health checks, and switches routes without requiring client-side profile changes. Two Go processes handle control logic and network enforcement separately, using SQLite for state and nftables plus Xray for traffic routing. TCP and UDP can be assigned independent exits, with geoip.dat support and custom rules to keep marketplace apps functional. The project emphasizes stability over direct connections and is designed for deployment on servers in Russian jurisdiction.
OpenAI Contractors Manually Review Real User Chats in Project Lily
OpenAI has engaged hundreds of external contractors to analyze actual user conversations with ChatGPT as part of its model improvement efforts. The reviewers, working under project Lily, examine real queries that may contain personal, medical, or other sensitive information despite the use of a Privacy Filter. Contractors summarize prompts, compare four model responses, and assign ratings from one to seven while flagging behaviors such as excessive sycophancy or inappropriate emojis. User identities are hidden and some data is filtered, yet OpenAI acknowledged that not all personal information is reliably removed. The same human review process is also employed by Anthropic for its Claude model. Users can opt out of future training use through account settings, although prior data remains unaffected.
UDP Proxies and QUIC Protocol: How Real IP Addresses Leak Through Anti-Detect Browsers
Anti-detect browser users relying on UDP-capable proxies face a hidden risk of real IP leakage when the browser fails to properly route UDP traffic. The QUIC protocol, which powers HTTP/3, runs over UDP and enables features like 0-RTT handshakes, independent streams, and connection migration that can bypass proxy routes. WebRTC connections using ICE, STUN, and TURN further increase exposure because they often attempt direct UDP paths outside the configured SOCKS5 proxy. Without deep network stack control such as TUN interfaces or socket interception, browsers may send WebRTC and QUIC packets through the host's real network interface. Aurorium Browser claims to solve this by natively supporting UDP proxying so that both QUIC and WebRTC traffic stays inside the tunnel. The article stresses that simply disabling WebRTC or forcing HTTP/2 fallback is insufficient and can itself create detectable anomalies for anti-fraud systems.