问题
my problem involves Google Chromium. Where on Windows I would download it from the Chromium Project Website and on a debian Linux distro I'd simply type "apt install chromium".
On Windows systems I use, Chromium provides a 404 when I attempt to sign in. However a fresh install of Linux, Chromium signs in without any error. This has been chalked up to API keys according to other Stack posts and Google Forums posts. What is different about Linux coded Chromium, why doesn't Windows Chromium have default keys for signing in?
Thanks for any clarity you can provide and if possible a solution to make Windows Chromium sign in properly without having to create some weird developer account through Google for the keys.
回答1:
I came here with the same question you have, and later discovered this Python script for injecting the API keys securely under macOS:
https://github.com/ezeeyahoo/ChromiumSyncEnabler
In the readme, the author says that as an alternative to generating your own keys:
You can also use keys used in chromium for linux platform:-
export GOOGLE_API_KEY="AIzaSyCkfPOPZXDKNn8hhgu3JrA62wIgC93d44k"
export GOOGLE_DEFAULT_CLIENT_ID="811574891467.apps.googleusercontent.com"
export GOOGLE_DEFAULT_CLIENT_SECRET="kdloedMFGdGla2P1zacGjAQh"
So, according to this, the Linux version simply comes with these ready-to-use keys.
Though I have no insight as to why this isn't done for Windows and macOS, I hope it's useful information.
来源：https://stackoverflow.com/questions/55367983/why-does-chromium-for-windows-need-api-keys-while-with-linux-it-works-without