Re: Gmail OAuth2 in git send-email
- From
Đoàn Trần Công Danh <congdanhqx@gmail.com>
- Date
- Jun 4, 2021, 01:49 UTC
- Message-ID
- <YLmGxcQ3s2gBbfe0@danh.dev>
- In-Reply-To
- <60b97dd1acd9d_3a18272087b@natae.notmuch>
On 2021-06-03 20:11:45-0500, Felipe Contreras <felipe.contreras@gmail.com> wrote:
Show 25 quoted lines
> Eric Sunshine wrote: > > Google requires 2fa to be enabled in order to create app passwords, > > That doesn't make sense. > > It's like complaining that you need to lose a limb in order to use > prostetics... > > App passwords are a suboptimal solution in case you cannot use 2fa for a > certain application. > > If you cannot use 2fa for any application, then don't enable 2fa, and > then you don't need an app password. Just use your regular password. > > > > 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 > > > > Thanks, that's an interesting bit of information, though if a person > > can't enable 2fa in the first place, then... (intentionally left > > blank) > > All you need to enable 2fa is demonstrate that you can *use* 2fa... So > you need an OTP client.
In the past, when I tried to enable 2FA, Google always asks for my Phone Number because of *security* and *safety* reason.
I tried to create a new Google account to double check my memory, Google now requires a phone number in order to *create* new Google accounts.
-- Danh