All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Benjamin Esquivel <benjamin.esquivel@gmail.com>, robert_henz@jabil.com
Cc: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	yocto@lists.yoctoproject.org
Subject: Re: [yocto] Git send-email blocked by gmail security changes (and how to fix it)
Date: Tue, 27 Sep 2022 16:16:32 +0200	[thread overview]
Message-ID: <CA+chaQdi_c2E78AHO_C8sDJrqUAt+4Tv+DCm0W16N5LaXnp8Zg@mail.gmail.com> (raw)
In-Reply-To: <D35FDEE6-48D5-4BC7-A204-8B074449B64F@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3308 bytes --]

On Thu, Sep 22, 2022 at 6:51 PM Benjamin Esquivel <
benjamin.esquivel@gmail.com> wrote:

>
>
> On Sep 21, 2022, at 11:07 PM, Nicolas Dechesne <
> nicolas.dechesne@linaro.org> wrote:
>
>
>
> On Thu, Sep 22, 2022 at 5:20 AM Benjamin Esquivel <
> benjamin.esquivel@gmail.com> wrote:
>
>> TL;DR Google App passwords are a workaround if your google password is
>> not working in git send-email.
>>
>> Hi,
>>
>> Not sure if this is the right list but I thought of sending it here as a
>> starter. I was following Stephen Jolley’s email for the Project status
>> where it has a section for ‘ways to contribute’ and a pointer to the
>> newcomers wiki. There is a link on How to Submit a Patch[1]  which has an
>> example on how to add a gmail account there. I followed it but in the end I
>> was blocked by an error stating that my 'Username and Password not
>> accepted’. Googled a proposed fix[2] to go to the gmail security settings
>> and enable "Access for less secure apps” but the solution is outdated as my
>> settings had a notice saying that it was removed some time ago.
>>
>> But I found that you can use another security feature from google called
>> app passwords[3]. And that means that it will give you one specific
>> password for your app needs. I tested this in the git send-email line and
>> it worked. I don’t know if others are doing this or if their previous
>> settings remain ok if these were configured before the recent security
>> resets that google has done.
>>
>
> You did the right thing. This is also how I use gmail with git-send-email.
>
>
>>
>> Is anyone struggling with this?
>>
>
> I don't remember if they disabled it for all gmail users, or only for
> users who enable 2FA.. but using apps specific token is what we should
> recommend to everyone.
>
>
>> Should we update the wiki to include this tip?
>>
>
> Yes, definitely. If you want to do it, please go ahead.  If you need help
> with that, let me know.
>
> I have just requested an account to the wiki and I’ll update that section
> once I get it :)
>

There was another thread about sending e-mails with git send-email this
week:
https://lists.openembedded.org/g/openembedded-core/message/171101
+Robert
which pointed to this longer explanation:
https://stackoverflow.com/questions/68238912/how-to-configure-and-use-git-send-email-to-work-with-gmail-to-email-patches-to

FWIW: I'm happily using msmtp with gmail account which is then used by git
send-email (through sendmail) with additional benefit that you can use the
same from mutt, cron, command line or whatever else you might want to send
e-mail (instead of using something specific to git send-email).

All you need to do is to install msmtp and short ~/.msmtprc like:
account default
auth login
from foo.bar@gmail.com
host smtp.gmail.com
user foo.bar@gmail.com
password foo.bar's.app.password

tls
tls_certcheck off
tls_starttls on

Then
git config sendemail.to <corresponding.ML>
e.g. openembedded-core@lists.openembedded.org in repos, so that you don't
need to manually type To: every time.

So yes, please update the wiki, but it's not as complicated as it might
seem (based on the questions about this topic), nor is it specific to
OE/Yocto.

Cheers,

[-- Attachment #2: Type: text/html, Size: 5236 bytes --]

      reply	other threads:[~2022-09-27 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  3:20 Git send-email blocked by gmail security changes (and how to fix it) Benjamin Esquivel
2022-09-22  6:07 ` [yocto] " Nicolas Dechesne
2022-09-22 16:51   ` Benjamin Esquivel
2022-09-27 14:16     ` Martin Jansa [this message]

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=CA+chaQdi_c2E78AHO_C8sDJrqUAt+4Tv+DCm0W16N5LaXnp8Zg@mail.gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=benjamin.esquivel@gmail.com \
    --cc=nicolas.dechesne@linaro.org \
    --cc=robert_henz@jabil.com \
    --cc=yocto@lists.yoctoproject.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 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.