{"thread":{"id":"55834","subject":"Gmail OAuth2 in git send-email","startedAt":"2021-06-03T05:03:26Z","lastAt":"2021-06-04T13:34:00Z","messageCount":31,"participants":["Bagas Sanjaya","ZheNing Hu","Jonathan Nieder","Eric Sunshine","Ævar Arnfjörð Bjarmason","Felipe Contreras","Konstantin Ryabitsev","Andreas Schwab","Michal Suchánek","Đoàn Trần Công Danh"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"426295","messageId":"d93a3024-ba8d-3469-2dba-2e0032334232@gmail.com","threadId":"55834","inReplyTo":null,"subject":"Gmail OAuth2 in git send-email","fromName":"Bagas Sanjaya","fromEmail":"bagasdotme@gmail.com","sentAt":"2021-06-03T05:02:08Z","receivedAt":"2021-06-03T05:03:26Z","isPatch":false,"sender":{"key":"bagasdotme@gmail.com","avatar":"https://avatars.githubusercontent.com/u/40219486?v=4"},"body":"Hi,\n\nFor most email providers, adding following .gitconfig is enough to \nseamlessly use git send-email:\n\n> [sendemail]\n> smtpEncryption = tls\n> smtpServer = \n> smtpUser = \n> smtpServerPort = 587\n\nBut for users that use Gmail (like me), we must either enable 2FA and \ngenerate app-specific password for use with git send-email, or enable \nless-secure app access. That's because Gmail prefers authenticating with \nOAuth2, but git send-email use plain text authentication instead.\n\nI personally prefer the latter because I know that I enabled less-secure \napp access only for duration of sending patches with git send-email \n(that is, I switched the trigger when I run git send-email).\n\nWe wonder whether git send-email can support Gmail OAuth2 so that we can \nseamlessly send patches without having to choose either action. But \nhowever, we have to create a GCP project [1] first in order to enable \nGmail API. This can be overkill for some folks, but unfortunately that's \nthe only way.\n\nIf we want to enable support for Gmail OAuth2, should we hands-off API \nconfiguration to git send-email users, or should we configure it on \nbehalf of them? Note that when we go the former approach, some Gmail \nusers simply can't afford GCP pricing for whatever reason (even don't \nhave any of required payment methods), whereas the latter approach we \nmust cover that cost (and Software Freedom Conservancy can raise funds \nneeded for it or git.git developers can pay it).\n\nThanks.\n\n[1]: https://developers.google.com/workspace/guides/create-project\n\n-- \nAn old man doll... just what I always wanted! - Clara\n"},{"id":"426299","messageId":"CAOLTT8TZhuK-Z_1MRrtreyg-jhHkCn8HEPJUOGM74ur8mVgLOQ@mail.gmail.com","threadId":"55834","inReplyTo":"d93a3024-ba8d-3469-2dba-2e0032334232@gmail.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"ZheNing Hu","fromEmail":"adlternative@gmail.com","sentAt":"2021-06-03T05:48:56Z","receivedAt":"2021-06-03T05:49:23Z","isPatch":false,"sender":{"key":"adlternative@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58138461?v=4"},"body":"Hi,\n\nBagas Sanjaya 于2021年6月3日周四 下午1:05写道：\n>\n> Hi,\n>\n> For most email providers, adding following .gitconfig is enough to\n> seamlessly use git send-email:\n>\n> > [sendemail]\n> > smtpEncryption = tls\n> > smtpServer = \n> > smtpUser = \n> > smtpServerPort = 587\n>\n> But for users that use Gmail (like me), we must either enable 2FA and\n> generate app-specific password for use with git send-email, or enable\n> less-secure app access. That's because Gmail prefers authenticating with\n> OAuth2, but git send-email use plain text authentication instead.\n>\n> I personally prefer the latter because I know that I enabled less-secure\n> app access only for duration of sending patches with git send-email\n> (that is, I switched the trigger when I run git send-email).\n>\n> We wonder whether git send-email can support Gmail OAuth2 so that we can\n> seamlessly send patches without having to choose either action. But\n> however, we have to create a GCP project [1] first in order to enable\n> Gmail API. This can be overkill for some folks, but unfortunately that's\n> the only way.\n>\n> If we want to enable support for Gmail OAuth2, should we hands-off API\n> configuration to git send-email users, or should we configure it on\n> behalf of them? Note that when we go the former approach, some Gmail\n> users simply can't afford GCP pricing for whatever reason (even don't\n> have any of required payment methods), whereas the latter approach we\n> must cover that cost (and Software Freedom Conservancy can raise funds\n> needed for it or git.git developers can pay it).\n>\n\nI met the same question as you before. [1] (write by chinese)\nWe need cumbersome operations to allow gmail to agree to use git send-email.\nI also want to know if send-email can be made more convenient\n(to reduce some configuration problems with gmail).\n\n[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/\n"},{"id":"426300","messageId":"YLhx7nIptHUwXfBD@google.com","threadId":"55834","inReplyTo":"d93a3024-ba8d-3469-2dba-2e0032334232@gmail.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2021-06-03T06:08:46Z","receivedAt":"2021-06-03T06:09:00Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nBagas Sanjaya wrote:\n\n> We wonder whether git send-email can support Gmail OAuth2 so that we can\n> seamlessly send patches without having to choose either action. But however,\n> we have to create a GCP project [1] first in order to enable Gmail API. This\n> can be overkill for some folks, but unfortunately that's the only way.\n\nYes, that's how I have mutt and other tools working with my Gmail\naccount set up. See [1] for details.\n\n> If we want to enable support for Gmail OAuth2, should we hands-off API\n> configuration to git send-email users, or should we configure it on behalf\n> of them? Note that when we go the former approach, some Gmail users simply\n> can't afford GCP pricing for whatever reason\n\nI didn't have to pay for GCP in order to set this up; I only had to\nfollow the instructions at\nhttps://developers.google.com/identity/protocols/oauth2 to create a\nclient ID and client secret for oauth access.\n\nAlas, I don't think Git can provide its own client secret to do this\nout of the box. I could imagine Git providing a way to supply an API\nkey at build time, but distros would need to go through a procedure\nsimilar to [2] to make use of it for their own builds. If someone\nwants to set that up, I think that would make sense as its _own_\nseparate package --- e.g. a \"sendgmail\" command that \"git send-email\"\ncould use via the --sendmail-cmd option. That way, it would be useful\nfor a variety of calling programs and not just Git.\n\nThanks and hope that helps,\nJonathan\n\n[1] https://bugs.debian.org/905551;msg=5\n[2] https://www.chromium.org/developers/how-tos/api-keys\n"},{"id":"426301","messageId":"CAPig+cRvCd5fG18n=XsqVLRcPHWJ1XxGvrkfxDY0fg3OgRbR2w@mail.gmail.com","threadId":"55834","inReplyTo":"YLhx7nIptHUwXfBD@google.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2021-06-03T06:26:46Z","receivedAt":"2021-06-03T06:27:16Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Thu, Jun 3, 2021 at 2:09 AM Jonathan Nieder wrote:\n> Bagas Sanjaya wrote:\n> > We wonder whether git send-email can support Gmail OAuth2 so that we can\n> > seamlessly send patches without having to choose either action. But however,\n> > we have to create a GCP project [1] first in order to enable Gmail API. This\n> > can be overkill for some folks, but unfortunately that's the only way.\n>\n> Yes, that's how I have mutt and other tools working with my Gmail\n> account set up. See [1] for details.\n> [1] https://bugs.debian.org/905551;msg=5\n\nThat link leads to a \"no results\" page. This link seems to work:\nhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905551\n"},{"id":"426309","messageId":"878s3r73g3.fsf@evledraar.gmail.com","threadId":"55834","inReplyTo":"YLhx7nIptHUwXfBD@google.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-06-03T08:28:37Z","receivedAt":"2021-06-03T08:33:22Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"\nOn Wed, Jun 02 2021, Jonathan Nieder wrote:\n\n> Hi,\n>\n> Bagas Sanjaya wrote:\n>\n>> We wonder whether git send-email can support Gmail OAuth2 so that we can\n>> seamlessly send patches without having to choose either action. But however,\n>> we have to create a GCP project [1] first in order to enable Gmail API. This\n>> can be overkill for some folks, but unfortunately that's the only way.\n>\n> Yes, that's how I have mutt and other tools working with my Gmail\n> account set up. See [1] for details.\n>\n>> If we want to enable support for Gmail OAuth2, should we hands-off API\n>> configuration to git send-email users, or should we configure it on behalf\n>> of them? Note that when we go the former approach, some Gmail users simply\n>> can't afford GCP pricing for whatever reason\n>\n> I didn't have to pay for GCP in order to set this up; I only had to\n> follow the instructions at\n> https://developers.google.com/identity/protocols/oauth2 to create a\n> client ID and client secret for oauth access.\n>\n> Alas, I don't think Git can provide its own client secret to do this\n> out of the box. I could imagine Git providing a way to supply an API\n> key at build time, but distros would need to go through a procedure\n> similar to [2] to make use of it for their own builds. If someone\n> wants to set that up, I think that would make sense as its _own_\n> separate package --- e.g. a \"sendgmail\" command that \"git send-email\"\n> could use via the --sendmail-cmd option. That way, it would be useful\n> for a variety of calling programs and not just Git.\n\nIt's been a while but I set this up at some point, why would git or\ndistros need to make/register a private key? Last I checked you can take\nsoftware like git-send-email or whatever, and just register a new\n\"jonathan's e-mail sending script\" with Google's OAuth thingy.\n\nThat \"jonathan's e-mail sending script\" happens to be git-send-email\nwith a bit of configuration isn't something they know or care about.\n\nThat seems like a much better approach than some centralized solution,\nsince as you note doing that will require some authority to manage keys\netc, and presumably if \"jonathan's e-mail sending script\" inadvertently\nstarts using git-send-email.perl to send spam, that would currently not\nresult in ban on \"ævar's e-mail sending script\", but if the two were\nregistered as the same application Google might overzelously ban those\nas two tenticles of the same misbehaving \"app\".\n\n"},{"id":"426336","messageId":"60b9158f92812_258801208e0@natae.notmuch","threadId":"55834","inReplyTo":"878s3r73g3.fsf@evledraar.gmail.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-06-03T17:46:55Z","receivedAt":"2021-06-03T17:47:12Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Ævar Arnfjörð Bjarmason wrote:\n> On Wed, Jun 02 2021, Jonathan Nieder wrote:\n> > Bagas Sanjaya wrote:\n\n> >> We wonder whether git send-email can support Gmail OAuth2 so that we can\n> >> seamlessly send patches without having to choose either action. But however,\n> >> we have to create a GCP project [1] first in order to enable Gmail API. This\n> >> can be overkill for some folks, but unfortunately that's the only way.\n> >\n> > Yes, that's how I have mutt and other tools working with my Gmail\n> > account set up. See [1] for details.\n> >\n> >> If we want to enable support for Gmail OAuth2, should we hands-off API\n> >> configuration to git send-email users, or should we configure it on behalf\n> >> of them? Note that when we go the former approach, some Gmail users simply\n> >> can't afford GCP pricing for whatever reason\n> >\n> > I didn't have to pay for GCP in order to set this up; I only had to\n> > follow the instructions at\n> > https://developers.google.com/identity/protocols/oauth2 to create a\n> > client ID and client secret for oauth access.\n> >\n> > Alas, I don't think Git can provide its own client secret to do this\n> > out of the box. I could imagine Git providing a way to supply an API\n> > key at build time, but distros would need to go through a procedure\n> > similar to [2] to make use of it for their own builds. If someone\n> > wants to set that up, I think that would make sense as its _own_\n> > separate package --- e.g. a \"sendgmail\" command that \"git send-email\"\n> > could use via the --sendmail-cmd option. That way, it would be useful\n> > for a variety of calling programs and not just Git.\n> \n> It's been a while but I set this up at some point, why would git or\n> distros need to make/register a private key? Last I checked you can take\n> software like git-send-email or whatever, and just register a new\n> \"jonathan's e-mail sending script\" with Google's OAuth thingy.\n> \n> That \"jonathan's e-mail sending script\" happens to be git-send-email\n> with a bit of configuration isn't something they know or care about.\n\nIf Google requires a client secret, then it can't be used with open\nsource applications. Period.\n\nSure, you could create a developer account, create an app, get a client\nid and secret, put into your authentication script, and the finally do\nthe authentication.\n\nOpen a browser with the link, type your password, verify on your phone\nwith a 2FA app or whatever.\n\nAnd finally you'll get a token. Which will have to be refreshed\nregularly.\n\n\nOr you can just create an app password.\n\nCheers.\n\n-- \nFelipe Contreras"},{"id":"426338","messageId":"20210603180851.5tbnuvfb6auxrhvm@nitro.local","threadId":"55834","inReplyTo":"d93a3024-ba8d-3469-2dba-2e0032334232@gmail.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Konstantin Ryabitsev","fromEmail":"konstantin@linuxfoundation.org","sentAt":"2021-06-03T18:08:51Z","receivedAt":"2021-06-03T18:08:55Z","isPatch":false,"sender":{"key":"konstantin@linuxfoundation.org","avatar":"https://gravatar.com/avatar/7cb8827c6de56e1bd2dea16508c6708aa43feed3bf3813bcdacecdf96ceadd79?d=mp&s=160"},"body":"On Thu, Jun 03, 2021 at 12:02:08PM +0700, Bagas Sanjaya wrote:\n> But for users that use Gmail (like me), we must either enable 2FA and\n> generate app-specific password for use with git send-email\n\nIs there a general problem with this approach? Gmail has been my\nrecommendation for everyone needing a free email account -- it's still\npossible to configure it to be perfectly usable with patch-based workflows,\neven if it has its own ideas about web ui treading.\n\nThe fact that Gmail forces folks to enable 2fa for app passwords is an added\nbonus in my book. :)\n\nThere are other alternatives, but they are not gratis or don't work well for\nsending patches. I'm also aware that gmail is not reliable for certain\ngeographical locales, so it's not a solution that suits everyone. We have\nrecently partnered with migadu.com and will start providing email accounts for\nLinux devs who cannot reliably use any other solution either due to their\nemployer doing nasty things to outgoing mail, or some other reason. At $20 a\nyear, migadu's pricing is hard to beat, though I know it's not for everyone.\n\n-K\n"},{"id":"426339","messageId":"CAPig+cT2fJqsptU0YpNQ=nhvU2Tu19zdHXxCin8fUkSkd97m4A@mail.gmail.com","threadId":"55834","inReplyTo":"20210603180851.5tbnuvfb6auxrhvm@nitro.local","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2021-06-03T18:25:42Z","receivedAt":"2021-06-03T18:25:55Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Thu, Jun 3, 2021 at 2:09 PM Konstantin Ryabitsev\n wrote:\n> On Thu, Jun 03, 2021 at 12:02:08PM +0700, Bagas Sanjaya wrote:\n> > But for users that use Gmail (like me), we must either enable 2FA and\n> > generate app-specific password for use with git send-email\n>\n> Is there a general problem with this approach? Gmail has been my\n> recommendation for everyone needing a free email account -- it's still\n> possible to configure it to be perfectly usable with patch-based workflows,\n> even if it has its own ideas about web ui treading.\n>\n> The fact that Gmail forces folks to enable 2fa for app passwords is an added\n> bonus in my book. :)\n\nThe 2fa requirement is a problem for those of us who don't have\nsmartphones or SMS. (I see now that they also offer 8-digit backup\ncodes to print out for 2fa; perhaps that might be a workable option,\nthough I haven't tested it.)\n"},{"id":"426340","messageId":"874keeyfl5.fsf@igel.home","threadId":"55834","inReplyTo":"60b9158f92812_258801208e0@natae.notmuch","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Andreas Schwab","fromEmail":"schwab@linux-m68k.org","sentAt":"2021-06-03T18:21:10Z","receivedAt":"2021-06-03T18:29:09Z","isPatch":false,"sender":{"key":"schwab@linux-m68k.org","avatar":"https://avatars.githubusercontent.com/u/2175493?v=4"},"body":"On Jun 03 2021, Felipe Contreras wrote:\n\n> If Google requires a client secret, then it can't be used with open\n> source applications. Period.\n\nhttps://invent.kde.org/pim/kmailtransport/-/blob/master/src/kmailtransport/plugins/smtp/smtpjob.cpp#L31\n\nAndreas.\n\n-- \nAndreas Schwab, schwab@linux-m68k.org\nGPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1\n\"And now for something completely different.\"\n"},{"id":"426341","messageId":"20210603183220.47nx7f2aazk6wy33@nitro.local","threadId":"55834","inReplyTo":"CAPig+cT2fJqsptU0YpNQ=nhvU2Tu19zdHXxCin8fUkSkd97m4A@mail.gmail.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Konstantin Ryabitsev","fromEmail":"konstantin@linuxfoundation.org","sentAt":"2021-06-03T18:32:20Z","receivedAt":"2021-06-03T18:33:24Z","isPatch":false,"sender":{"key":"konstantin@linuxfoundation.org","avatar":"https://gravatar.com/avatar/7cb8827c6de56e1bd2dea16508c6708aa43feed3bf3813bcdacecdf96ceadd79?d=mp&s=160"},"body":"On Thu, Jun 03, 2021 at 02:25:42PM -0400, Eric Sunshine wrote:\n> > The fact that Gmail forces folks to enable 2fa for app passwords is an added\n> > bonus in my book. :)\n> \n> The 2fa requirement is a problem for those of us who don't have\n> smartphones or SMS. (I see now that they also offer 8-digit backup\n> codes to print out for 2fa; perhaps that might be a workable option,\n> though I haven't tested it.)\n\nI'm not going to argue too much, but I'd say that someone who's looking for\nsolution to use with git-send-email is *likely* going to have access to a\nsmartphone. :)\n\nIt's also possible to use TOTP without a smartphone (e.g. via a desktop app),\nthough this would largely defeat the purpose.\n\n-K\n"},{"id":"426342","messageId":"60b926ff6ef35_39cbe920875@natae.notmuch","threadId":"55834","inReplyTo":"874keeyfl5.fsf@igel.home","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-06-03T19:01:19Z","receivedAt":"2021-06-03T19:01:50Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Andreas Schwab wrote:\n> On Jun 03 2021, Felipe Contreras wrote:\n> \n> > If Google requires a client secret, then it can't be used with open\n> > source applications. Period.\n> \n> https://invent.kde.org/pim/kmailtransport/-/blob/master/src/kmailtransport/plugins/smtp/smtpjob.cpp#L31\n\nYes, they are doing something wrong (puting a *secret* value on a public\nplace), so?\n\nIf somebody were to report that to Google that app probably would get\nbanned.\n\n-- \nFelipe Contreras\n"},{"id":"426343","messageId":"20210603190231.GT8544@kitsune.suse.cz","threadId":"55834","inReplyTo":"20210603183220.47nx7f2aazk6wy33@nitro.local","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Michal Suchánek","fromEmail":"msuchanek@suse.de","sentAt":"2021-06-03T19:02:31Z","receivedAt":"2021-06-03T19:02:35Z","isPatch":false,"sender":{"key":"msuchanek@suse.de","avatar":"https://avatars.githubusercontent.com/u/787652?v=4"},"body":"On Thu, Jun 03, 2021 at 02:32:20PM -0400, Konstantin Ryabitsev wrote:\n> On Thu, Jun 03, 2021 at 02:25:42PM -0400, Eric Sunshine wrote:\n> > > The fact that Gmail forces folks to enable 2fa for app passwords is an added\n> > > bonus in my book. :)\n> > \n> > The 2fa requirement is a problem for those of us who don't have\n> > smartphones or SMS. (I see now that they also offer 8-digit backup\n> > codes to print out for 2fa; perhaps that might be a workable option,\n> > though I haven't tested it.)\n> \n> I'm not going to argue too much, but I'd say that someone who's looking for\n> solution to use with git-send-email is *likely* going to have access to a\n> smartphone. :)\n\nI do have a smartphone. Due to the battery life of smartphones I don't\nhave access to it most of the time.\n\n> \n> It's also possible to use TOTP without a smartphone (e.g. via a desktop app),\n> though this would largely defeat the purpose.\n\nThere are also TOTP hardware tokens but I haven't tried one. I think\nthat the U2F tokens are better supported anyway.\n\nIf you want some sort of real security I would avoid smartphones and go\nfor hardware tokens. If you want to fulfill arbitrary requiremens\nworkarounds that emulate a smartphone well enough exist. For TOTP you\ndon't even need an emulator, only a QR code reader (in case the site\ninsists on using QR code and does not show the plaintext) and a desktop\nTOTP application.\n\nThanks\n\nMichal\n"},{"id":"426344","messageId":"60b928374d90e_39cbe920835@natae.notmuch","threadId":"55834","inReplyTo":"CAPig+cT2fJqsptU0YpNQ=nhvU2Tu19zdHXxCin8fUkSkd97m4A@mail.gmail.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-06-03T19:06:31Z","receivedAt":"2021-06-03T19:07:52Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Eric Sunshine wrote:\n> On Thu, Jun 3, 2021 at 2:09 PM Konstantin Ryabitsev\n> wrote:\n> > On Thu, Jun 03, 2021 at 12:02:08PM +0700, Bagas Sanjaya wrote:\n> > > But for users that use Gmail (like me), we must either enable 2FA and\n> > > generate app-specific password for use with git send-email\n> >\n> > Is there a general problem with this approach? Gmail has been my\n> > recommendation for everyone needing a free email account -- it's still\n> > possible to configure it to be perfectly usable with patch-based workflows,\n> > even if it has its own ideas about web ui treading.\n> >\n> > The fact that Gmail forces folks to enable 2fa for app passwords is an added\n> > bonus in my book. :)\n> \n> The 2fa requirement is a problem for those of us who don't have\n> smartphones or SMS.\n\nYou don't need either of those with an app password:\n\n https://support.google.com/mail/answer/185833/sign-in-using-app-passwords\n\nAnd of course you don't need them for the second step authentication\neither, you can use any OTP client:\n\n https://github.com/paolostivanin/OTPClient\n\nCheers.\n\n-- \nFelipe Contreras\n"},{"id":"426345","messageId":"20210603190756.ri5o4udl2bvusyhw@nitro.local","threadId":"55834","inReplyTo":"20210603190231.GT8544@kitsune.suse.cz","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Konstantin Ryabitsev","fromEmail":"konstantin@linuxfoundation.org","sentAt":"2021-06-03T19:07:56Z","receivedAt":"2021-06-03T19:08:00Z","isPatch":false,"sender":{"key":"konstantin@linuxfoundation.org","avatar":"https://gravatar.com/avatar/7cb8827c6de56e1bd2dea16508c6708aa43feed3bf3813bcdacecdf96ceadd79?d=mp&s=160"},"body":"On Thu, Jun 03, 2021 at 09:02:31PM +0200, Michal Suchánek wrote:\n> > I'm not going to argue too much, but I'd say that someone who's looking for\n> > solution to use with git-send-email is *likely* going to have access to a\n> > smartphone. :)\n> \n> I do have a smartphone. Due to the battery life of smartphones I don't\n> have access to it most of the time.\n\nAs a note, you wouldn't need to use it \"all the time\" -- just for the initial\nlogin via the browser. Once it's done and you set up the app passwords for\nSMTP/IMAP access, you would rarely ever need to access the TOTP token again.\n\n-K\n"},{"id":"426347","messageId":"20210603192301.GU8544@kitsune.suse.cz","threadId":"55834","inReplyTo":"20210603190756.ri5o4udl2bvusyhw@nitro.local","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Michal Suchánek","fromEmail":"msuchanek@suse.de","sentAt":"2021-06-03T19:23:01Z","receivedAt":"2021-06-03T19:23:05Z","isPatch":false,"sender":{"key":"msuchanek@suse.de","avatar":"https://avatars.githubusercontent.com/u/787652?v=4"},"body":"On Thu, Jun 03, 2021 at 03:07:56PM -0400, Konstantin Ryabitsev wrote:\n> On Thu, Jun 03, 2021 at 09:02:31PM +0200, Michal Suchánek wrote:\n> > > I'm not going to argue too much, but I'd say that someone who's looking for\n> > > solution to use with git-send-email is *likely* going to have access to a\n> > > smartphone. :)\n> > \n> > I do have a smartphone. Due to the battery life of smartphones I don't\n> > have access to it most of the time.\n> \n> As a note, you wouldn't need to use it \"all the time\" -- just for the initial\n> login via the browser. Once it's done and you set up the app passwords for\n> SMTP/IMAP access, you would rarely ever need to access the TOTP token again.\n\nI also avoid doing anything security sensitive on the smartphone. They\ntend to run old vulnerable software because smarphonde vendors aren't\nagile with fixes, and they are a rewarding target for hackers.\n\nGiven that your smartphone and our PC are typically connected to the\nsame network it is not difficult to correlate the two.\n\nThanks\n\nMichal\n"},{"id":"426370","messageId":"CAPig+cS74Ah3OyJPNQhvkdV6f7mkFgFQjHgfrrAE1gZsvN38RA@mail.gmail.com","threadId":"55834","inReplyTo":"60b928374d90e_39cbe920835@natae.notmuch","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2021-06-03T23:35:32Z","receivedAt":"2021-06-03T23:36:01Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Thu, Jun 3, 2021 at 3:06 PM Felipe Contreras\n wrote:\n> Eric Sunshine wrote:\n> > The 2fa requirement is a problem for those of us who don't have\n> > smartphones or SMS.\n>\n> You don't need either of those with an app password:\n>\n> https://support.google.com/mail/answer/185833/sign-in-using-app-passwords\n\nGoogle requires 2fa to be enabled in order to create app passwords,\nand to enable 2fa requires a phone or a physical security device, so\nI'm afraid I don't see how your suggestion is supposed to work for\npeople lacking such devices.\n\n> And of course you don't need them for the second step authentication\n> either, you can use any OTP client:\n>\n> https://github.com/paolostivanin/OTPClient\n\nThanks, that's an interesting bit of information, though if a person\ncan't enable 2fa in the first place, then... (intentionally left\nblank)\n"},{"id":"426371","messageId":"CAPig+cQX7PkPxGMe8oLKU-kqsas0vKoszLtntgNp3K+5SvBDNg@mail.gmail.com","threadId":"55834","inReplyTo":"20210603190756.ri5o4udl2bvusyhw@nitro.local","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2021-06-03T23:42:20Z","receivedAt":"2021-06-03T23:42:45Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Thu, Jun 3, 2021 at 3:08 PM Konstantin Ryabitsev\n wrote:\n> As a note, you wouldn't need to use it \"all the time\" -- just for the initial\n> login via the browser. Once it's done and you set up the app passwords for\n> SMTP/IMAP access, you would rarely ever need to access the TOTP token again.\n\nThanks, that's a helpful datapoint. Coupled with Felipe's tidbit about\nPC-based OTP clients, it sounds like this might almost be usable for\nsomeone without a phone (assuming 2fa can somehow be enabled).\n"},{"id":"426373","messageId":"60b97dd1acd9d_3a18272087b@natae.notmuch","threadId":"55834","inReplyTo":"CAPig+cS74Ah3OyJPNQhvkdV6f7mkFgFQjHgfrrAE1gZsvN38RA@mail.gmail.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-06-04T01:11:45Z","receivedAt":"2021-06-04T01:11:49Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Eric Sunshine wrote:\n> Google requires 2fa to be enabled in order to create app passwords,\n\nThat doesn't make sense.\n\nIt's like complaining that you need to lose a limb in order to use\nprostetics...\n\nApp passwords are a suboptimal solution in case you cannot use 2fa for a\ncertain application.\n\nIf you cannot use 2fa for any application, then don't enable 2fa, and\nthen you don't need an app password. Just use your regular password.\n\n> > And of course you don't need them for the second step authentication\n> > either, you can use any OTP client:\n> >\n> > https://github.com/paolostivanin/OTPClient\n> \n> Thanks, that's an interesting bit of information, though if a person\n> can't enable 2fa in the first place, then... (intentionally left\n> blank)\n\nAll you need to enable 2fa is demonstrate that you can *use* 2fa... So\nyou need an OTP client.\n\nCheers.\n\n-- \nFelipe Contreras\n"},{"id":"426375","messageId":"YLmGo8PZDAT90hj+@google.com","threadId":"55834","inReplyTo":"878s3r73g3.fsf@evledraar.gmail.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2021-06-04T01:49:23Z","receivedAt":"2021-06-04T01:49:39Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nÆvar Arnfjörð Bjarmason wrote:\n\n> It's been a while but I set this up at some point, why would git or\n> distros need to make/register a private key? Last I checked you can take\n> software like git-send-email or whatever, and just register a new\n> \"jonathan's e-mail sending script\" with Google's OAuth thingy.\n\nYes, that's what I do.\n\n[...]\n> That seems like a much better approach than some centralized solution,\n> since as you note doing that will require some authority to manage keys\n> etc, and presumably if \"jonathan's e-mail sending script\" inadvertently\n> starts using git-send-email.perl to send spam, that would currently not\n> result in ban on \"ævar's e-mail sending script\", but if the two were\n> registered as the same application Google might overzelously ban those\n> as two tenticles of the same misbehaving \"app\".\n\nI agree that it wouldn't be worth \"git send-email\" registering for its\nown API key, mostly because registering for API keys with every email\nprovider would be a distraction from what git send-email tries to do.\n\nOn the other hand, I would mind a perl library or a commandline tool\nthat git send-email calls having _its_ own API key. That would be\nhelpful to other programs that want to send email as well, and it\nwould help users who are not as patient as we are in trudging through\nthe multi-step process required. For example, it's nice that KMail,\nApple's Mail.app, and so on have their own API keys instead of every\nuser of those programs having to generate their own.\n\nOf course, that's a broader topic than Git; it's not something that we\non the Git list are uniquely positioned to do ourselves. I only\nmention it in case someone in this thread wants to write it. Then git\nsend-email could use such a library or point to such a tool in its\ndocumentation.\n\nThanks,\nJonathan\n"},{"id":"426376","messageId":"YLmGxcQ3s2gBbfe0@danh.dev","threadId":"55834","inReplyTo":"60b97dd1acd9d_3a18272087b@natae.notmuch","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Đoàn Trần Công Danh","fromEmail":"congdanhqx@gmail.com","sentAt":"2021-06-04T01:49:57Z","receivedAt":"2021-06-04T01:50:12Z","isPatch":false,"sender":{"key":"congdanhqx@gmail.com","avatar":"https://avatars.githubusercontent.com/u/42673067?v=4"},"body":"On 2021-06-03 20:11:45-0500, Felipe Contreras wrote:\n> Eric Sunshine wrote:\n> > Google requires 2fa to be enabled in order to create app passwords,\n> \n> That doesn't make sense.\n> \n> It's like complaining that you need to lose a limb in order to use\n> prostetics...\n> \n> App passwords are a suboptimal solution in case you cannot use 2fa for a\n> certain application.\n> \n> If you cannot use 2fa for any application, then don't enable 2fa, and\n> then you don't need an app password. Just use your regular password.\n> \n> > > And of course you don't need them for the second step authentication\n> > > either, you can use any OTP client:\n> > >\n> > > https://github.com/paolostivanin/OTPClient\n> > \n> > Thanks, that's an interesting bit of information, though if a person\n> > can't enable 2fa in the first place, then... (intentionally left\n> > blank)\n> \n> All you need to enable 2fa is demonstrate that you can *use* 2fa... So\n> you need an OTP client.\n\nIn the past, when I tried to enable 2FA, Google always asks for my\nPhone Number because of *security* and *safety* reason.\n\nI tried to create a new Google account to double check my memory,\nGoogle now requires a phone number in order to *create* new Google\naccounts.\n\n-- \nDanh\n"},{"id":"426377","messageId":"60b98adc7f8cb_3a25c2208c9@natae.notmuch","threadId":"55834","inReplyTo":"YLmGxcQ3s2gBbfe0@danh.dev","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-06-04T02:07:24Z","receivedAt":"2021-06-04T02:08:43Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Đoàn Trần Công Danh wrote:\n> On 2021-06-03 20:11:45-0500, Felipe Contreras wrote:\n> > All you need to enable 2fa is demonstrate that you can *use* 2fa... So\n> > you need an OTP client.\n> \n> In the past, when I tried to enable 2FA, Google always asks for my\n> Phone Number because of *security* and *safety* reason.\n> \n> I tried to create a new Google account to double check my memory,\n> Google now requires a phone number in order to *create* new Google\n> accounts.\n\nPresumably if you don't have a Google account, then don't have a\ngmail.com address, and you can't use Gmail.\n\nSo why would this thread interest you?\n\n-- \nFelipe Contreras"},{"id":"426378","messageId":"YLmLyT0XmQ/lOBKg@danh.dev","threadId":"55834","inReplyTo":"60b98adc7f8cb_3a25c2208c9@natae.notmuch","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Đoàn Trần Công Danh","fromEmail":"congdanhqx@gmail.com","sentAt":"2021-06-04T02:11:21Z","receivedAt":"2021-06-04T02:11:39Z","isPatch":false,"sender":{"key":"congdanhqx@gmail.com","avatar":"https://avatars.githubusercontent.com/u/42673067?v=4"},"body":"On 2021-06-03 21:07:24-0500, Felipe Contreras wrote:\n> Đoàn Trần Công Danh wrote:\n> > On 2021-06-03 20:11:45-0500, Felipe Contreras wrote:\n> > > All you need to enable 2fa is demonstrate that you can *use* 2fa... So\n> > > you need an OTP client.\n> > \n> > In the past, when I tried to enable 2FA, Google always asks for my\n> > Phone Number because of *security* and *safety* reason.\n> > \n> > I tried to create a new Google account to double check my memory,\n> > Google now requires a phone number in order to *create* new Google\n> > accounts.\n> \n> Presumably if you don't have a Google account, then don't have a\n> gmail.com address, and you can't use Gmail.\n> \n> So why would this thread interest you?\n\nThe first point ;)\n\n> > In the past, when I tried to enable 2FA, Google always asks for my\n> > Phone Number because of *security* and *safety* reason.\n\n-- \nDanh\n"},{"id":"426380","messageId":"YLmSd7ADvhdh33/O@google.com","threadId":"55834","inReplyTo":"YLmGo8PZDAT90hj+@google.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2021-06-04T02:39:51Z","receivedAt":"2021-06-04T02:39:56Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Jonathan Nieder wrote:\n\n> I agree that it wouldn't be worth \"git send-email\" registering for its\n> own API key, mostly because registering for API keys with every email\n> provider would be a distraction from what git send-email tries to do.\n>\n> On the other hand, I would mind a perl library or a commandline tool\n> that git send-email calls having _its_ own API key.\n\nAhem --- I *wouldn't* mind a perl library or commandline tool showing\nup that does this. Sorry for the confusion.\n\n> That would be\n> helpful to other programs that want to send email as well, and it\n> would help users who are not as patient as we are in trudging through\n> the multi-step process required. For example, it's nice that KMail,\n> Apple's Mail.app, and so on have their own API keys instead of every\n> user of those programs having to generate their own.\n\nThere's a sendgmail tool in\nhttps://github.com/google/gmail-oauth2-tools. It requires generating\nyour own API key but I suppose someone could package it up with an API\nkey for their package if they wish to.\n\nJonathan\n"},{"id":"426384","messageId":"60b9a1b2e402b_3a3b7e20899@natae.notmuch","threadId":"55834","inReplyTo":"YLmSd7ADvhdh33/O@google.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-06-04T03:44:50Z","receivedAt":"2021-06-04T03:46:07Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Jonathan Nieder wrote:\n> Jonathan Nieder wrote:\n\n> > That would be\n> > helpful to other programs that want to send email as well, and it\n> > would help users who are not as patient as we are in trudging through\n> > the multi-step process required. For example, it's nice that KMail,\n> > Apple's Mail.app, and so on have their own API keys instead of every\n> > user of those programs having to generate their own.\n> \n> There's a sendgmail tool in\n> https://github.com/google/gmail-oauth2-tools. It requires generating\n> your own API key but I suppose someone could package it up with an API\n> key for their package if they wish to.\n\nAPI keys and client secrets are supposed to be *secret*. You must not\ngenerate *public* packages with them.\n\nI don't know why people insist on using something that isn't supposed to\nbe used.\n\nIf you want to use a 2FA-enabled account with git, then generate an app\npassword, and use that.\n\nCheers.\n\n-- \nFelipe Contreras\n"},{"id":"426385","messageId":"60b9a1d25b63f_3a3b7e208fd@natae.notmuch","threadId":"55834","inReplyTo":"YLmLyT0XmQ/lOBKg@danh.dev","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-06-04T03:45:22Z","receivedAt":"2021-06-04T03:46:38Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Đoàn Trần Công Danh wrote:\n> On 2021-06-03 21:07:24-0500, Felipe Contreras wrote:\n> > Đoàn Trần Công Danh wrote:\n> > > On 2021-06-03 20:11:45-0500, Felipe Contreras wrote:\n> > > > All you need to enable 2fa is demonstrate that you can *use* 2fa... So\n> > > > you need an OTP client.\n> > > \n> > > In the past, when I tried to enable 2FA, Google always asks for my\n> > > Phone Number because of *security* and *safety* reason.\n> > > \n> > > I tried to create a new Google account to double check my memory,\n> > > Google now requires a phone number in order to *create* new Google\n> > > accounts.\n> > \n> > Presumably if you don't have a Google account, then don't have a\n> > gmail.com address, and you can't use Gmail.\n> > \n> > So why would this thread interest you?\n> \n> The first point ;)\n\nWhich is?\n\n-- \nFelipe Contreras"},{"id":"426388","messageId":"CAPig+cSXbCTymdrUOZwFBeUNMWuhnGb91Ar9Jth2cHCG2xav+g@mail.gmail.com","threadId":"55834","inReplyTo":"60b97dd1acd9d_3a18272087b@natae.notmuch","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2021-06-04T04:10:09Z","receivedAt":"2021-06-04T04:10:37Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Thu, Jun 3, 2021 at 9:11 PM Felipe Contreras\n wrote:\n> Eric Sunshine wrote:\n> > Google requires 2fa to be enabled in order to create app passwords,\n>\n> That doesn't make sense.\n\nWhat doesn't make sense? My statement? Or Google's requirements?\n\n> It's like complaining that you need to lose a limb in order to use\n> prostetics...\n> App passwords are a suboptimal solution in case you cannot use 2fa for a\n> certain application.\n\nNevertheless, that's what Google requires.\n\n> If you cannot use 2fa for any application, then don't enable 2fa, and\n> then you don't need an app password. Just use your regular password.\n\nGoogle has been clamping down on \"regular password\" use for\nthird-party applications/sign-ins for several years now and they\nheavily discourage it. It is still possible to do it, though, by\nenabling \"Less secure apps\" explicitly[1]. However, when \"Less secure\napps\" is enabled, they regularly send messages \"strongly suggesting\"\nturning it off. I won't be surprised if the \"Less secure apps\" option\ndisappears at some point.\n\n> > Thanks, that's an interesting bit of information, though if a person\n> > can't enable 2fa in the first place, then... (intentionally left\n> > blank)\n>\n> All you need to enable 2fa is demonstrate that you can *use* 2fa... So\n> you need an OTP client.\n\nI'd be happy to see concrete instructions explaining how to accomplish\nall of this since each time I attempted it, Google's instructions led\nme in endless circles, with each cycle always asking for (er,\nrequiring) my non-existent phone number.\n\n[1]: https://support.google.com/accounts/answer/6010255/less-secure-apps-amp-your-google-account\n"},{"id":"426397","messageId":"YLm4dn4INFPhg2OI@danh.dev","threadId":"55834","inReplyTo":"60b9a1d25b63f_3a3b7e208fd@natae.notmuch","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Đoàn Trần Công Danh","fromEmail":"congdanhqx@gmail.com","sentAt":"2021-06-04T05:21:58Z","receivedAt":"2021-06-04T05:22:17Z","isPatch":false,"sender":{"key":"congdanhqx@gmail.com","avatar":"https://avatars.githubusercontent.com/u/42673067?v=4"},"body":"On 2021-06-03 22:45:22-0500, Felipe Contreras wrote:\n> Đoàn Trần Công Danh wrote:\n>> On 2021-06-03 21:07:24-0500, Felipe Contreras wrote:\n>> > Đoàn Trần Công Danh wrote:\n>> > > On 2021-06-03 20:11:45-0500, Felipe Contreras wrote:\n>> > > > All you need to enable 2fa is demonstrate that you can *use* 2fa... So\n>> > > > you need an OTP client.\n>> > > \n>> > > In the past, when I tried to enable 2FA, Google always asks for my\n>> > > Phone Number because of *security* and *safety* reason.\n>> > > \n>> > > I tried to create a new Google account to double check my memory,\n>> > > Google now requires a phone number in order to *create* new Google\n>> > > accounts.\n>> > \n>> > Presumably if you don't have a Google account, then don't have a\n>> > gmail.com address, and you can't use Gmail.\n>> > \n>> > So why would this thread interest you?\n>> \n>> The first point ;)\n> \n> Which is?\n\nWhich is the point I specificly copy-pasted after that comment,\nand it's also the point you stripped out.\n\nI guess it's my bad that I wasn't very clear in the original comment.\nSo, here is the quote:\n\n>> > > In the past, when I tried to enable 2FA, Google always asks for my\n>> > > Phone Number because of *security* and *safety* reason.\n\n-- \nDanh\n"},{"id":"426398","messageId":"60b9bba4b792c_3bd685208ec@natae.notmuch","threadId":"55834","inReplyTo":"CAPig+cSXbCTymdrUOZwFBeUNMWuhnGb91Ar9Jth2cHCG2xav+g@mail.gmail.com","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-06-04T05:35:32Z","receivedAt":"2021-06-04T05:35:51Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Eric Sunshine wrote:\n> On Thu, Jun 3, 2021 at 9:11 PM Felipe Contreras\n> wrote:\n> > Eric Sunshine wrote:\n> > > Google requires 2fa to be enabled in order to create app passwords,\n> >\n> > That doesn't make sense.\n> \n> What doesn't make sense? My statement?\n\nYour statement.\n\n> > It's like complaining that you need to lose a limb in order to use\n> > prostetics...\n> > App passwords are a suboptimal solution in case you cannot use 2fa for a\n> > certain application.\n> \n> Nevertheless, that's what Google requires.\n\nNo. Google doesn't require app passwords, nor 2fa.\n\n> > If you cannot use 2fa for any application, then don't enable 2fa, and\n> > then you don't need an app password. Just use your regular password.\n> \n> Google has been clamping down on \"regular password\" use for\n> third-party applications/sign-ins for several years now and they\n> heavily discourage it.\n\nPerhaps, but they don't requier 2fa. If you don't want to use 2fa, then\nuse regular passwords.\n\nOr just don't use Gmail.\n\n-- \nFelipe Contreras\n"},{"id":"426399","messageId":"60b9c17ae2306_3bd68520833@natae.notmuch","threadId":"55834","inReplyTo":"YLm4dn4INFPhg2OI@danh.dev","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-06-04T06:00:26Z","receivedAt":"2021-06-04T06:01:40Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Đoàn Trần Công Danh wrote:\n> On 2021-06-03 22:45:22-0500, Felipe Contreras wrote:\n> > Đoàn Trần Công Danh wrote:\n> >> On 2021-06-03 21:07:24-0500, Felipe Contreras wrote:\n> >> > Đoàn Trần Công Danh wrote:\n> >> > > On 2021-06-03 20:11:45-0500, Felipe Contreras wrote:\n> >> > > > All you need to enable 2fa is demonstrate that you can *use* 2fa... So\n> >> > > > you need an OTP client.\n> >> > > \n> >> > > In the past, when I tried to enable 2FA, Google always asks for my\n> >> > > Phone Number because of *security* and *safety* reason.\n> >> > > \n> >> > > I tried to create a new Google account to double check my memory,\n> >> > > Google now requires a phone number in order to *create* new Google\n> >> > > accounts.\n> >> > \n> >> > Presumably if you don't have a Google account, then don't have a\n> >> > gmail.com address, and you can't use Gmail.\n> >> > \n> >> > So why would this thread interest you?\n> >> \n> >> The first point ;)\n> > \n> > Which is?\n> \n> Which is the point I specificly copy-pasted after that comment,\n> and it's also the point you stripped out.\n> \n> I guess it's my bad that I wasn't very clear in the original comment.\n> So, here is the quote:\n> \n> >> > > In the past, when I tried to enable 2FA, Google always asks for my\n> >> > > Phone Number because of *security* and *safety* reason.\n\nI still don't see what is your point.\n\nIf you don't have a Gmail account, then why do you care about particular\nways to authenticate into a Gmail account?\n\n-- \nFelipe Contreras"},{"id":"426400","messageId":"YLnG1Npa9rMYyWJJ@danh.dev","threadId":"55834","inReplyTo":"60b9c17ae2306_3bd68520833@natae.notmuch","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Đoàn Trần Công Danh","fromEmail":"congdanhqx@gmail.com","sentAt":"2021-06-04T06:23:16Z","receivedAt":"2021-06-04T06:24:20Z","isPatch":false,"sender":{"key":"congdanhqx@gmail.com","avatar":"https://avatars.githubusercontent.com/u/42673067?v=4"},"body":"On 2021-06-04 01:00:26-0500, Felipe Contreras wrote:\n> Đoàn Trần Công Danh wrote:\n> > >> > > In the past, when I tried to enable 2FA, Google always asks for my\n> > >> > > Phone Number because of *security* and *safety* reason.\n> \n> I still don't see what is your point.\n> \n> If you don't have a Gmail account, then why do you care about particular\n> ways to authenticate into a Gmail account?\n\nI have a GMail account, and I have 2 FA enabled already.\n\nI was talking about my experience when I first enabled 2FA,\n\nGoogle required me to provide me a phone number, which I hadn't\nprovided prior to that point.\n\nSo, someone else, who haven't enable 2FA and haven't provided Google\nphone number, may hesitate to enable 2FA.\n\nThe second point is me trying to validate my (usually bad) memory.\n\n-- \nDanh\n"},{"id":"426418","messageId":"60ba2b7bf4006_f5b33208f8@natae.notmuch","threadId":"55834","inReplyTo":"YLnG1Npa9rMYyWJJ@danh.dev","subject":"Re: Gmail OAuth2 in git send-email","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-06-04T13:32:44Z","receivedAt":"2021-06-04T13:34:00Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Đoàn Trần Công Danh wrote:\n> On 2021-06-04 01:00:26-0500, Felipe Contreras wrote:\n> > Đoàn Trần Công Danh wrote:\n> > > >> > > In the past, when I tried to enable 2FA, Google always asks for my\n> > > >> > > Phone Number because of *security* and *safety* reason.\n> > \n> > I still don't see what is your point.\n> > \n> > If you don't have a Gmail account, then why do you care about particular\n> > ways to authenticate into a Gmail account?\n> \n> I have a GMail account, and I have 2 FA enabled already.\n> \n> I was talking about my experience when I first enabled 2FA,\n\nOK, but I was talking about ways to authenticate into your existing\nGmail account, which was supposed to be the topic of this thread.\n\nCheers.\n\n-- \nFelipe Contreras"}]}