<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Yubikey on WhyNotHugo</title><link>https://whynothugo.nl/tags/yubikey/</link><description>Recent content in Yubikey on WhyNotHugo</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 09 Mar 2024 11:42:44 +0100</lastBuildDate><atom:link href="https://whynothugo.nl/tags/yubikey/posts.xml" rel="self" type="application/rss+xml"/><item><title>Extending an expired GPG key</title><link>https://whynothugo.nl/journal/2023/07/13/extending-an-expired-gpg-key/</link><pubDate>Thu, 13 Jul 2023 00:00:00 +0000</pubDate><guid>https://whynothugo.nl/journal/2023/07/13/extending-an-expired-gpg-key/</guid><description>Slightly over a year ago, I set up a new hardware-backed GPG key on my yubikey device. Today I needed to sign a release, and noticed my key expired two days ago. It&amp;rsquo;s time to renew it.
Possible approaches[permalink] When a key expires, there are three alternatives on how to address this:
Generate a new key pair. This requires updating my public key everywhere (e.g.: on services that use my public key, in the README for projects where I sign releases, etc), which is somewhat of a nuisance.</description></item><item><title>Using a Yubikey for both GPG and TOTP</title><link>https://whynothugo.nl/journal/2023/03/13/using-a-yubikey-for-both-gpg-and-totp/</link><pubDate>Mon, 13 Mar 2023 18:39:00 +0100</pubDate><guid>https://whynothugo.nl/journal/2023/03/13/using-a-yubikey-for-both-gpg-and-totp/</guid><description>I&amp;rsquo;ve written before on how I use a Yubikey for hardware-based GPG and 2FA on the web. I also use it for TOTP. That is, the Yubikey itself generates those common &amp;ldquo;authenticator codes&amp;rdquo; like many other Authenticator apps. But the secret seed is saved into hardware that does not support revealing it, instead of being handled by a regular app on a network-connected device.
A nasty issue I&amp;rsquo;ve been dealing with is that when I signed something using GPG, the key would no longer work for TOTP unless I killed the gpg-agent.</description></item><item><title>Using a Yubikey for GPG</title><link>https://whynothugo.nl/journal/2022/07/11/using-a-yubikey-for-gpg/</link><pubDate>Mon, 11 Jul 2022 00:00:00 +0000</pubDate><guid>https://whynothugo.nl/journal/2022/07/11/using-a-yubikey-for-gpg/</guid><description>I&amp;rsquo;ve written recently on how I use a Yubikey as a hardware security token for two factor authentication.
One item I was missing was GPG, and this was mostly because setting up GPG is a bit tricker to set up and I simply hadn&amp;rsquo;t had the time. My previous key recently expired, so this is a good time to address that.
This article explains the basics of how Yubikey + GPG works, and how to get started.</description></item><item><title>How I secure my setup with a YubiKey</title><link>https://whynothugo.nl/journal/2022/05/07/how-i-secure-my-setup-with-a-yubikey/</link><pubDate>Sat, 07 May 2022 00:00:00 +0000</pubDate><guid>https://whynothugo.nl/journal/2022/05/07/how-i-secure-my-setup-with-a-yubikey/</guid><description>YubiKeys[permalink] I have a pair of YubiKey 5C NFC, which I use for authentication a lot. They&amp;rsquo;re small USB-C authentication devices which can generate multiple types of keys and are usable for different types of authentication.
There's also a USB-A version if USB-C ports aren't your thing. The keys generated on-device cannot be extracted, which means that the only way to steal the keys is to physically steal the device itself.</description></item></channel></rss>