Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: gentoo-dev@l.g.o
Cc: pr@g.o, sultan@g.o
Subject: Re: [gentoo-dev] Re: [RFC] News Item: OAuth2 Credentials Removed from Chromium
Date: Sun, 08 Aug 2021 15:58:37
Message-Id: 449b4693cdee03f4fe0142ec33214ee1f4dcc057.camel@gentoo.org
In Reply to: [gentoo-dev] Re: [RFC] News Item: OAuth2 Credentials Removed from Chromium by "Jason A. Donenfeld"
1 On Sun, 2021-08-08 at 14:39 +0200, Jason A. Donenfeld wrote:
2 > v2 after brief IRC discussion
3 > ---
4 >
5 > Title: OAuth2 Credentials Removed from Chromium
6 > Author: Jason A. Donenfeld
7 > Posted: 2021-08-08
8 > Revision: 1
9 > News-Item-Format: 2.0
10 > Display-If-Installed: www-client/chromium
11 >
12 > In March of this year, Google announced that OAuth2 credentials would be revoked
13 > for distros shipping Chromium. This was covered in multiple places at the time,
14 > such as [1,2,3]. Around that time, with 89.0.4389.82, Gentoo removed OAuth2
15 > credentials from its packages. However, they slipped back in shortly after. As
16 > a result, some users [4] have found that recently Google's SSO does not persist
17 > between browser sessions; e.g. you have to log back into GMail every time you
18 > open your browser. Today's changes [5] restore the old behavior we had in March,
19 > of not shipping Gentoo OAuth2 credentials. If you find that certain Google
20 > services are no longer working, you may wish to set these flags, obtaining
21 > credentials by following the instructions at [6]. However, even without
22 > supplying such credentials, Google's SSO now should be working as expected.
23
24 Please split this into multiple shorter paragraphs. It's very hard to
25 follow such a huge wall of text.
26
27 >
28 > There are now two options for passing these tokens to Chromium via
29 > /etc/chromium/default:
30 >
31 > 1. GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET environment
32 > variables:
33 > export GOOGLE_DEFAULT_CLIENT_ID="<client-id>"
34 > export GOOGLE_DEFAULT_CLIENT_SECRET="<client-secret>"
35 >
36 > 2. --oauth2-client-id and --oauth2-client-secret= command line switches:
37 > CHROMIUM_FLAGS+=" --oauth2-client-id=<client-id>"
38 > CHROMIUM_FLAGS+=" --oauth2-client-secret=<client-secret>"
39 >
40 > Alternatively these environment variables and command line switches may be given
41 > at the command line for ad-hoc testing.
42 >
43 > [1] https://archlinux.org/news/chromium-losing-sync-support-in-early-march/
44 > [2] https://bodhi.fedoraproject.org/updates/FEDORA-2021-48866282e5
45 > [3] https://hackaday.com/2021/01/26/whats-the-deal-with-chromium-on-linux-google-at-odds-with-package-maintainers/
46 > [4] https://bugs.gentoo.org/791871
47 > [5] https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fce48ef271bbcaee9afdf0481294da167e665a9b
48 > [6] http://www.chromium.org/developers/how-tos/api-keys
49 >
50
51 --
52 Best regards,
53 Michał Górny

Replies