All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Esquivel <benjamin.esquivel@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: Git send-email blocked by gmail security changes  (and how to fix it)
Date: Wed, 21 Sep 2022 20:20:33 -0700	[thread overview]
Message-ID: <7313BA28-2972-4FD7-8E37-27196FAF5B8A@gmail.com> (raw)

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

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.

Is anyone struggling with this?
Should we update the wiki to include this tip?

Regards,

Benjamin

[1] https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded <https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded>
[2] https://support.google.com/mail/thread/5621336?hl=en <https://support.google.com/mail/thread/5621336?hl=en>
[3] https://support.google.com/accounts/answer/185833 <https://support.google.com/accounts/answer/185833>

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

             reply	other threads:[~2022-09-22  3:20 UTC|newest]

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

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=7313BA28-2972-4FD7-8E37-27196FAF5B8A@gmail.com \
    --to=benjamin.esquivel@gmail.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.