workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: workflows@vger.kernel.org
Subject: Gmail (was: Re: lore+lei: part 2, now with IMAP)
Date: Mon, 15 Nov 2021 19:34:00 +0100	[thread overview]
Message-ID: <CAMuHMdXCbjx9CdkjVnp0cYhrjZCyGWYYraai=xSXXNbYjO2K1g@mail.gmail.com> (raw)
In-Reply-To: <lorelei.part2.202111121411.sznnvkvcywfbdghl@meerkat.local>

Hi Konstantin,

On Fri, Nov 12, 2021 at 8:13 PM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
> Continuing on my previous email about setting up lei with lore.kernel.org,
> here's the next installment. As with the previous part, this will be posted on
> people.kernel.org as well as here.
>
> # lore+lei: part 2, now with IMAP

> ### The same with Gmail
>
> If you are a Gmail user and aren't already using IMAP, then you will need to
> jump through a few additional hoops before you are able to get going. Google
> is attempting to enhance the security of your account by restricting how much
> can be done with just your Google username and password, so services like IMAP
> are not available without setting up a special "app password" that can only be
> used for mail access.
>
> Enabling app passwords requires that you first enable 2-factor authentication,
> and then generate a random app password to use with IMAP. Please follow the
> process described in the following Google document:
> https://support.google.com/mail/answer/185833

On a related subject, I am using Gmail for email (e.g. patch review),
but not for actual patch submission (git send-email through my ISP's
SMTP server). I do have app passwords set up for git send-email on
my laptop (if I ever need to send patches while on the road, barely
used so far) and for backing up email using getmail.

Recently I received an email from Google that my account may be "at
greater risk of targeted attack", and that they recommend enrolling
into Google's strongest account security offering, the Advanced
Protection Program.  Apparently this makes use of a hardware token,
the Titan Security Key.  I have no idea what kind of criteria are
used to reach out to people (might be people involved with important
FLOSS projects, who knows? ;-), but the other family members haven't
received this.

Perhaps other people are in the same boat?
Do you have any advice here? Thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2021-11-15 18:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 19:13 lore+lei: part 2, now with IMAP Konstantin Ryabitsev
2021-11-15 18:34 ` Geert Uytterhoeven [this message]
2021-11-15 21:46   ` Gmail (was: Re: lore+lei: part 2, now with IMAP) Konstantin Ryabitsev
2021-11-16  8:01     ` Geert Uytterhoeven
2021-11-16  8:04       ` Drew DeVault
2021-11-16  8:26         ` Geert Uytterhoeven
2021-11-16  8:29           ` Drew DeVault
2021-11-16 13:49             ` Konstantin Ryabitsev
2021-11-16 13:51               ` Drew DeVault
2021-11-16 14:04                 ` Konstantin Ryabitsev
2021-11-16 13:35       ` Konstantin Ryabitsev
2021-11-16 12:18     ` Han-Wen Nienhuys
2021-11-22 14:37 ` lore+lei: part 2, now with IMAP Jani Nikula
2021-11-22 15:07   ` Konstantin Ryabitsev

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='CAMuHMdXCbjx9CdkjVnp0cYhrjZCyGWYYraai=xSXXNbYjO2K1g@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=workflows@vger.kernel.org \
    --subject='Gmail (was: Re: lore+lei: part 2, now with IMAP)' \
    /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

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).