Re: Gmail OAuth2 in git send-email

From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Jonathan Nieder" <jrnieder@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, Git <git@vger.kernel.org>
Subject: Re: Gmail OAuth2 in git send-email
Date: Thu, 03 Jun 2021 22:44:50 -0500	[thread overview]
Message-ID: <60b9a1b2e402b_3a3b7e20899@natae.notmuch> (raw)
In-Reply-To: <YLmSd7ADvhdh33/O@google.com>

Jonathan Nieder wrote:
> Jonathan Nieder wrote:

> >                                                      That would be
> > helpful to other programs that want to send email as well, and it
> > would help users who are not as patient as we are in trudging through
> > the multi-step process required.  For example, it's nice that KMail,
> > Apple's Mail.app, and so on have their own API keys instead of every
> > user of those programs having to generate their own.
> 
> There's a sendgmail tool in
> https://github.com/google/gmail-oauth2-tools.  It requires generating
> your own API key but I suppose someone could package it up with an API
> key for their package if they wish to.

API keys and client secrets are supposed to be *secret*. You must not
generate *public* packages with them.

I don't know why people insist on using something that isn't supposed to
be used.

If you want to use a 2FA-enabled account with git, then generate an app
password, and use that.

Cheers.

-- 
Felipe Contreras