Google announced that Android 17 is the first mobile operating system to support Encrypted Client Hello (ECH), a TLS privacy feature that hides destination domain names from network observers. The release also enforces new local-network permissions and enables Certificate Transparency by default, and it allows telecoms to block phones from often malicious 2G access points. These changes are aimed at U.S. users and others who rely on Android devices for everyday browsing and messaging.
ECH addresses a long-standing gap in HTTPS: while the content of web sessions is encrypted, the website hostname was previously exposed in the Server Name Indication field of the TLS handshake. That allowed internet service providers, Wi-Fi operators, corporate networks, and unauthorized snoopers to identify the sites a user visited. Google said that encrypting the destination name from the start means network providers can no longer easily see which websites or apps are being accessed, especially when combined with Android's Private DNS feature.
The protection only works for supported websites and apps. Android's developer documentation says ECH is enabled by default on Android 17, API level 37, but applications need an ECH-capable networking library. Google advised developers to upgrade to OkHttp 5.5.0 and enable ECH, and the platform includes a mechanism called ECH GREASE to make protected connections harder to spot when a server does not support the feature. ECH is not a VPN, and observers may still see destination IP addresses, traffic volume, and timing, and it does not hide DNS requests on its own.
The 2G kill switch addresses a security threat from SMS blasters and false cellular base stations. These devices can broadcast a strong signal that forces nearby phones to drop LTE or 5G and connect through older 2G technology, allowing attackers to bypass anti-spam measures and deliver phishing texts. Android's documentation warns that a phone may keep scanning for 2G base stations even when its carrier has retired 2G service, leaving it vulnerable to downgrade attacks, so disabling 2G prevents the device from connecting to those networks.
There is a practical trade-off for travelers. Turning off 2G can affect coverage while roaming in places where 2G is still part of the network mix, and Android says the security-driven disablement will remain in effect during roaming. Google cannot reliably detect 2G roaming because 2G lacks mutual authentication, which is the same design weakness that makes fake-base-station attacks possible, so users may have no service until they manually re-enable the older network type.
The ECH and 2G changes are part of a larger Android 17 network-security package. Local Network Protection is now enforced, requiring app permission before connecting to other devices on a user's local network, and Certificate Transparency is enabled by default to make it easier to spot fraudulent certificates. These protections will take effect without user action, but full benefits depend on developers and telecoms supporting the changes in their programs, services, and networks.
More software news from TechManNews.
