Topic

Certificate Transparency

🇵🇹Sep 1

Android 17 Adds Local Network Protection and Strengthens Wi-Fi Privacy Controls

Android 17 introduces Local Network Protection, requiring apps to obtain explicit permission before scanning or connecting to devices on the same Wi-Fi network. The feature limits unauthorized discovery of TVs, cameras, printers, consoles and other local equipment that could previously be used to build detailed user profiles. The update also enables Encrypted Client Hello by default to hide domain names during HTTPS handshakes from network observers. Certificate Transparency is now activated by default to detect fraudulent or mis-issued certificates that could enable interception attacks. Additional safeguards block forced downgrades to insecure 2G networks often exploited by fake base stations for SMS-based fraud. These changes collectively reduce passive tracking and man-in-the-middle risks without disrupting legitimate local network functions such as media casting.

BoletimSec•Privacy & Surveillance
🇷🇺Aug 23

Trusting Russian Root Certificates and Monitoring Domestic CT Logs

The article examines risks associated with installing Russian root certificates issued by the Ministry of Digital Development. It explains how these certificates, when trusted, enable potential MitM attacks through TSPU infrastructure by allowing on-the-fly issuance of fraudulent certificates for foreign domains. Yandex Browser stands out by enforcing Certificate Transparency checks for domestic certificates, unlike other browsers that disable CT validation in the presence of added roots. Three primary domestic CT logs are maintained by Yandex, VK, and the Ministry, with log lists updated annually. A Python script is provided to query these logs directly and verify SCT inclusion for any certificate. The piece also notes limitations of existing web monitors such as ct.tlscc.ru when dealing with newer log endpoints.

Habr•Policy & Regulation