this post was submitted on 05 Jun 2024
46 points (78.0% liked)
Open Source
31128 readers
416 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I already use
pass
("the unix password manager") and there's a pretty decent extension that lets it handle 2fa: https://github.com/tadfisher/pass-otpWorth noting that this somewhat defeats the purpose of 2fa if you put your GitHub password in the same store as the one used for otp. Nevertheless, this let's me sign on to 2fa services from the command line without purchasing a USB dongle or needing a smartphone on-hand.
Your two factors shift to possession of your password vault + knowledge of the password to it. You're okay IMO.
You also still get the anti-replay benefits of the OTPs, though that might be a bit moot with TLS everywhere.
You're right, I should have been more specific.
If you're already storing your password using
pass
, you aren't getting 3 factors withpass-otp
unless you store the otp generation into a separate store.For services like GitHub that mandate using an otp, it's convenient without being an effective loss of 2fa to store everything together.