{"id":42837,"date":"2023-02-16T23:15:45","date_gmt":"2023-02-16T23:15:45","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2023\/02\/16\/google-security-certificate-log-change-broke-android-apps-the-register\/"},"modified":"2023-02-16T23:17:48","modified_gmt":"2023-02-16T23:17:48","slug":"google-security-certificate-log-change-broke-android-apps-the-register","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2023\/02\/16\/google-security-certificate-log-change-broke-android-apps-the-register\/","title":{"rendered":"Google security certificate log change broke Android apps \u2022 The Register"},"content":{"rendered":"

<\/a>\n<\/p>\n

\n

Google this week reversed an overhaul of one in all its security-related file codecs after the transition broke Android apps.<\/p>\n

In November, 2021, Google introduced adjustments to the format of its Chrome Certificates Transparency log checklist file and, in August, 2022, notified builders whose apps is perhaps affected that it will cease publishing legacy log checklist information on October 17, 2022.<\/p>\n

A certificate transparency log<\/a> is an append-only public ledger of newly issued safety certificates trusted for issues like HTTPS encryption. The general purpose of that is to permit organizations and netizens to simply monitor and audit<\/a> these newest certs, and spot and invalidate rogue or wrongly issued certificates that may very well be used to, as an illustration, impersonate companies and software program builders. Google vacuums up<\/a> these logs from certificates authorities, and publishes this consolidated document because the Chrome Certificates Transparency log.<\/p>\n

\n