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: Tue, 16 Nov 2021 08:35:45 -0500	[thread overview]
Message-ID: <20211116133545.frkailn7cto6z6lo@meerkat.local> (raw)
In-Reply-To: <CAMuHMdUjfGJcZt1J7+XUHdCBhK2Wvm=KkKEOrG3ieFsPqTcgng@mail.gmail.com>

On Tue, Nov 16, 2021 at 09:01:35AM +0100, Geert Uytterhoeven wrote:
> > 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.
> 
> Thanks for the explanation.
> Given it uses U2F, that means I cannot use the Nitrokey Start for that?

No, the Start doesn't support u2f. Their Nitrokey 3 should support all
operation modes that kernel devs would want (PGP, Fido2), but they have been
hit by the same chips shortage as everyone else, so the launch has been
delayed multiple times. I should get mine soon, hopefully, so I'll be able to
review it.

If you just want a U2F token for your Google account, then you can get any
common Fido2 device, including the Titan key. If you only use it for Google
and a handful of other sites supporting u2f, then you only need it extremely
occasionally and it can just hang on your keychain and look pretty the rest of
the time.

-K

  parent reply	other threads:[~2021-11-16 13:35 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
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 [this message]
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=20211116133545.frkailn7cto6z6lo@meerkat.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).