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

On Mon, Nov 15, 2021 at 07:34:00PM +0100, Geert Uytterhoeven wrote:
> 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. 

Well, I'm sure they wouldn't mind if you paid them money for a "Titan Security
key", but it's really just a rebranded Chinese-made U2F token and, as such,
not any different from any other U2F security key. You can get one from
Nitrokey (nitrokey.com) or SoloKeys (solokeys.com). I *do* recommend using a
hardware token for your Google account, seeing as it's increasingly tied to so
much of our online identity.

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

It's anyone's guess, but it's probably based on analyzing various account
dumps a-la haveibeenpwned.com or Mozilla's Firefox Monitor. It doesn't
necessarily mean that you have anything in particular to worry about.

Best regards,
-K

  reply	other threads:[~2021-11-15 22:58 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 ` Gmail (was: Re: lore+lei: part 2, now with IMAP) Geert Uytterhoeven
2021-11-15 21:46   ` Konstantin Ryabitsev [this message]
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=20211115214641.lxo5zhttrqq6mx2z@nitro.local \
    --to=konstantin@linuxfoundation.org \
    --cc=geert@linux-m68k.org \
    --cc=workflows@vger.kernel.org \
    --subject='Re: 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).