/explore
|
You are here 
|
perishablepress.com | ||
| | | | |
nolanlawson.com
|
|
| | | | | I recently picked up a YubiKey, because we use them at work and I was impressed with how simple and easy-to-use they are. I've been really happy with it so far - enough to write a blog post about it. Basically, YubiKey works like this: whenever you need to do two-factor authentication (2FA), you just... | |
| | | | |
www.dannyguo.com
|
|
| | | | | [AI summary] The author discusses their decision to migrate from Authy to Bitwarden for managing two-factor authentication (2FA) codes, highlighting issues with Authy's backup, syncing, and CPU usage, while detailing the benefits and setup of Bitwarden. | |
| | | | |
imrannazar.com
|
|
| | | | | I've been slowly removing Google apps from my life, and one of the last ones left is Authenticator. In this post I look at migrating codes out of Authenticator to a command-line OTP tool, and the steps involved. | |
| | | | |
rcoh.me
|
|
| | | I always wondered how Google Authenticator style 2-factor codes worked. The process of going from QR code to rotating 6-digit pin seemed a bit magical. A few days ago, my curiosity found itself coupled with some free time. Here's what I found: What's in the QR Code I scanned the QR code from Github with a barcode scanning app. Here's what's inside: otpauth://totp/Github:rcoh?secret=onswg4tforrw6zdf&issuer=Github Not too surprising. It tells us the protocol, TOTP, who is issuing this OTP code (Github), and most importantly the secret:1 | ||
