From: ZheNing Hu <adlternative@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Gmail OAuth2 in git send-email
Date: Thu, 3 Jun 2021 13:48:56 +0800 [thread overview]
Message-ID: <CAOLTT8TZhuK-Z_1MRrtreyg-jhHkCn8HEPJUOGM74ur8mVgLOQ@mail.gmail.com> (raw)
In-Reply-To: <d93a3024-ba8d-3469-2dba-2e0032334232@gmail.com>
Hi,
Bagas Sanjaya <bagasdotme@gmail.com> 于2021年6月3日周四 下午1:05写道:
>
> Hi,
>
> For most email providers, adding following .gitconfig is enough to
> seamlessly use git send-email:
>
> > [sendemail]
> > smtpEncryption = tls
> > smtpServer = <server>
> > smtpUser = <email>
> > smtpServerPort = 587
>
> But for users that use Gmail (like me), we must either enable 2FA and
> generate app-specific password for use with git send-email, or enable
> less-secure app access. That's because Gmail prefers authenticating with
> OAuth2, but git send-email use plain text authentication instead.
>
> I personally prefer the latter because I know that I enabled less-secure
> app access only for duration of sending patches with git send-email
> (that is, I switched the trigger when I run git send-email).
>
> We wonder whether git send-email can support Gmail OAuth2 so that we can
> seamlessly send patches without having to choose either action. But
> however, we have to create a GCP project [1] first in order to enable
> Gmail API. This can be overkill for some folks, but unfortunately that's
> the only way.
>
> If we want to enable support for Gmail OAuth2, should we hands-off API
> configuration to git send-email users, or should we configure it on
> behalf of them? Note that when we go the former approach, some Gmail
> users simply can't afford GCP pricing for whatever reason (even don't
> have any of required payment methods), whereas the latter approach we
> must cover that cost (and Software Freedom Conservancy can raise funds
> needed for it or git.git developers can pay it).
>
I met the same question as you before. [1] (write by chinese)
We need cumbersome operations to allow gmail to agree to use git send-email.
I also want to know if send-email can be made more convenient
(to reduce some configuration problems with gmail).
[1]: https://adlternative.github.io/archlinux%E4%B8%8A%E7%9A%84git-send-email%E9%97%AE%E9%A2%98%E7%9A%84%E8%A7%A3%E5%86%B3%E6%96%B9%E6%A1%88/
next prev parent reply other threads:[~2021-06-03 5:49 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 [this message]
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
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=CAOLTT8TZhuK-Z_1MRrtreyg-jhHkCn8HEPJUOGM74ur8mVgLOQ@mail.gmail.com \
--to=adlternative@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).