archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <>
To: Konstantin Ryabitsev <>
Subject: Re: Gmail (was: Re: lore+lei: part 2, now with IMAP)
Date: Tue, 16 Nov 2021 09:01:35 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20211115214641.lxo5zhttrqq6mx2z@nitro.local>

Hi Konstantin,

On Mon, Nov 15, 2021 at 10:46 PM Konstantin Ryabitsev
<> wrote:
> 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 ( or SoloKeys ( I *do* recommend using a
> hardware token for your Google account, seeing as it's increasingly tied to so
> much of our online identity.

Thanks for the explanation.
Given it uses U2F, that means I cannot use the Nitrokey Start for that?



Geert Uytterhoeven -- There's lots of Linux beyond ia32 --

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-16  8:01 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
2021-11-16  8:01     ` Geert Uytterhoeven [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \
    --subject='Re: Gmail (was: Re: lore+lei: part 2, now with IMAP)' \

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