Re: Gmail OAuth2 in git send-email
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Jun 3, 2021, 18:25 UTC
- Message-ID
- <CAPig+cT2fJqsptU0YpNQ=nhvU2Tu19zdHXxCin8fUkSkd97m4A@mail.gmail.com>
- In-Reply-To
- <20210603180851.5tbnuvfb6auxrhvm@nitro.local>
On Thu, Jun 3, 2021 at 2:09 PM Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
Show 11 quoted lines
> 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. (I see now that they also offer 8-digit backup codes to print out for 2fa; perhaps that might be a workable option, though I haven't tested it.)