Google закрывает сторонний доступ к Chrome Sync API

В ходе аудита компания Google обнаружила, что некоторые сторонние продукты, основанные на коде Chromium, используют ключи, позволяющие получить доступ к некоторым API и сервисам Google, предназначенным для внутреннего использования. В частности к google_default_client_id и к google_default_client_secret. Благодаря этому пользователь имеет возможность получать доступ к своим собственным Chrome Sync данным (таким, как закладки) не только в Chrome но и в сторонних браузерах, основанных на коде Chromium. Оправдываясь усилиями по повышению безопасности Google закрывает доступ стороннему програмному обеспечению к вышеозначенным API. Данное решение вступает в силу начиная с 15 марта этого года.

В связи с этим многие дистрибутивы рассматривают возможность полного отказа от Chromium в своих поставках. Среди них: Arch Linux, Fedora, Debian, Slackware, OpenSUSE и другие.


Hi Chromium Developer,

We are writing to let you know that starting March 15, 2021, end users of Chromium and Chromium OS derivatives using google_default_client_id and google_default_client_secret on their build configuration will no longer be able to sign into their Google Accounts.
What do I need to know?

During a recent audit, we discovered that some 3rd-party Chromium-based browsers had keys that were allowed to access Google APIs and services that are reserved for Google use only. Chrome Sync is the most notable of these APIs. В частности к google_default_client_id и google_default_client_secret.

In practice, this means that a user would be able to access their personal Chrome Sync data (such as bookmarks) not just with Chrome, but also with a non-Google, Chromium-based browser. Please note that users would only be able to access their own Chrome Sync data, and only a small fraction of users of Chromium based browsers were impacted. We have no reason to believe that user data is being abused or accessed by anyone other than the users themselves.

As part of Google’s efforts to improve user data security, we are removing access from Chromium and Chromium OS derivatives that used google_default_client_id and google_default_client_secret on their build configuration to Google-exclusive APIs starting on March 15, 2021. Guidance for vendors of Chromium derivative products is available on the Chromium wiki.
What does this mean for my users?

Users of products that are incorrectly using these APIs will notice that they won’t be able to log into their Google Accounts in those products anymore.

For users who accessed Google features (like Chrome Sync) through a 3rd-party Chromium-based browser, their data will continue to be available in their Google Account, and data that they have stored locally will continue to be available locally.

As always, users can view and manage their data through Google Chrome, Chrome OS, and/or on the My Google Activity page, and they can also download their data from the Google Takeout page, and/or delete it from this page.
What do I need to do?

To avoid disruption, follow the instructions for configuring and building Chromium derivatives in the Chromium Wiki (link provided above).

Possible ways to implement this are:

Removing google_default_client_id and google_default_client_secret from your build configuration.
Passing the —allow-browser-signin=false flag at startup.

Your projects that may be affected by this change are listed below:

Arch Linux Chromium (arch-linux-chromium)

If you have any questions or require assistance, please contact embedd…


The Google Chrome Team