Android 17 introduces system-level Encrypted Client Hello to enhance network privacy

Google’s latest Android update, Android 17, incorporates system-wide Encrypted Client Hello (ECH) to bolster user privacy by encrypting server name information and reducing passive surveillance, alongside other security enhancements.

Google is adding a new layer of network privacy to Android 17, with Encrypted Client Hello set to be enabled at system level for supported traffic. According to reporting by The Hacker News, the aim is to make it harder for network operators and internet providers to see which websites or apps a device is reaching, reducing the value of traffic analysis and other forms of passive surveillance.

The key change is ECH, a TLS extension that encrypts the server name information normally exposed during connection set-up. Google’s Android Developers documentation says this means intermediaries can no longer easily identify the hostname an app is connecting to, while guidance for developers explains that support depends on networking libraries, network security settings and target SDK configuration. The company also says ECH works alongside Private DNS, which helps obscure domain lookups and limits the metadata available for profiling.

Google has also enabled ECH GREASE by default in Android 17, a compatibility measure designed to make encrypted and non-encrypted connections look similar to outside observers. That should make it harder for networks that do not yet support ECH to single out protected traffic. In parallel, the open-source OkHttp library has built ECH support into its core, giving third-party Android developers a direct route to adopt the feature inside their own apps.

Beyond ECH, the update tightens several other network protections. The Hacker News reported that Local Network Protection will require explicit user permission before apps can scan or contact devices on a home Wi-Fi network. Android 17 also enables Certificate Transparency by default, pushing websites towards public logging of SSL/TLS certificates to help expose forged certificates. In addition, mobile operators can disable 2G by default for subscribers, a move intended to reduce exposure to downgrade attacks, rogue base stations and SMS blasters used in fraud campaigns.

Disclaimer: This content is intended for informational purposes only. Readers are advised to exercise their own judgement, conduct due diligence, or consult a qualified expert before acting on any information provided.