All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Git Users <git@vger.kernel.org>
Subject: Re: Gmail OAuth2 in git send-email
Date: Fri, 4 Jun 2021 08:49:57 +0700	[thread overview]
Message-ID: <YLmGxcQ3s2gBbfe0@danh.dev> (raw)
In-Reply-To: <60b97dd1acd9d_3a18272087b@natae.notmuch>

On 2021-06-03 20:11:45-0500, Felipe Contreras <felipe.contreras@gmail.com> wrote:
> 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

  reply	other threads:[~2021-06-04  1:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  5:02 Gmail OAuth2 in git send-email Bagas Sanjaya
2021-06-03  5:48 ` ZheNing Hu
2021-06-03  6:08 ` Jonathan Nieder
2021-06-03  6:26   ` Eric Sunshine
2021-06-03  8:28   ` Ævar Arnfjörð Bjarmason
2021-06-03 17:46     ` Felipe Contreras
2021-06-03 18:21       ` Andreas Schwab
2021-06-03 19:01         ` Felipe Contreras
2021-06-04  1:49     ` Jonathan Nieder
2021-06-04  2:39       ` Jonathan Nieder
2021-06-04  3:44         ` Felipe Contreras
2021-06-03 18:08 ` Konstantin Ryabitsev
2021-06-03 18:25   ` Eric Sunshine
2021-06-03 18:32     ` Konstantin Ryabitsev
2021-06-03 19:02       ` Michal Suchánek
2021-06-03 19:07         ` Konstantin Ryabitsev
2021-06-03 19:23           ` Michal Suchánek
2021-06-03 23:42           ` Eric Sunshine
2021-06-03 19:06     ` Felipe Contreras
2021-06-03 23:35       ` Eric Sunshine
2021-06-04  1:11         ` Felipe Contreras
2021-06-04  1:49           ` Đoàn Trần Công Danh [this message]
2021-06-04  2:07             ` Felipe Contreras
2021-06-04  2:11               ` Đoàn Trần Công Danh
2021-06-04  3:45                 ` Felipe Contreras
2021-06-04  5:21                   ` Đoàn Trần Công Danh
2021-06-04  6:00                     ` Felipe Contreras
2021-06-04  6:23                       ` Đoàn Trần Công Danh
2021-06-04 13:32                         ` Felipe Contreras
2021-06-04  4:10           ` Eric Sunshine
2021-06-04  5:35             ` Felipe Contreras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YLmGxcQ3s2gBbfe0@danh.dev \
    --to=congdanhqx@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=sunshine@sunshineco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.