Re: Gmail OAuth2 in git send-email

From: "Michal Suchánek" <msuchanek@suse.de>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Git Users <git@vger.kernel.org>
Subject: Re: Gmail OAuth2 in git send-email
Date: Thu, 3 Jun 2021 21:23:01 +0200	[thread overview]
Message-ID: <20210603192301.GU8544@kitsune.suse.cz> (raw)
In-Reply-To: <20210603190756.ri5o4udl2bvusyhw@nitro.local>

On Thu, Jun 03, 2021 at 03:07:56PM -0400, Konstantin Ryabitsev wrote:
> On Thu, Jun 03, 2021 at 09:02:31PM +0200, Michal Suchánek wrote:
> > > I'm not going to argue too much, but I'd say that someone who's looking for
> > > solution to use with git-send-email is *likely* going to have access to a
> > > smartphone. :)
> > 
> > I do have a smartphone. Due to the battery life of smartphones I don't
> > have access to it most of the time.
> 
> As a note, you wouldn't need to use it "all the time" -- just for the initial
> login via the browser. Once it's done and you set up the app passwords for
> SMTP/IMAP access, you would rarely ever need to access the TOTP token again.

I also avoid doing anything security sensitive on the smartphone. They
tend to run old vulnerable software because smarphonde vendors aren't
agile with fixes, and they are a rewarding target for hackers.

Given that your smartphone and our PC are typically connected to the
same network it is not difficult to correlate the two.

Thanks

Michal