Re: Gmail OAuth2 in git send-email

From: Felipe Contreras <felipe.contreras@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, Git Users <git@vger.kernel.org>
Subject: Re: Gmail OAuth2 in git send-email
Date: Thu, 03 Jun 2021 14:06:31 -0500	[thread overview]
Message-ID: <60b928374d90e_39cbe920835@natae.notmuch> (raw)
In-Reply-To: <CAPig+cT2fJqsptU0YpNQ=nhvU2Tu19zdHXxCin8fUkSkd97m4A@mail.gmail.com>

Eric Sunshine wrote:
> On Thu, Jun 3, 2021 at 2:09 PM Konstantin Ryabitsev
> <konstantin@linuxfoundation.org> wrote:
> > On Thu, Jun 03, 2021 at 12:02:08PM +0700, Bagas Sanjaya wrote:
> > > But for users that use Gmail (like me), we must either enable 2FA and
> > > generate app-specific password for use with git send-email
> >
> > Is there a general problem with this approach? Gmail has been my
> > recommendation for everyone needing a free email account -- it's still
> > possible to configure it to be perfectly usable with patch-based workflows,
> > even if it has its own ideas about web ui treading.
> >
> > The fact that Gmail forces folks to enable 2fa for app passwords is an added
> > bonus in my book. :)
> 
> The 2fa requirement is a problem for those of us who don't have
> smartphones or SMS.

You don't need either of those with an app password:

  https://support.google.com/mail/answer/185833/sign-in-using-app-passwords

And of course you don't need them for the second step authentication
either, you can use any OTP client:

  https://github.com/paolostivanin/OTPClient

Cheers.

-- 
Felipe Contreras