Same. Maximum comfort since Bitwarden autofills and puts the token in your clipboard, you dont have to change apps or need you smartphone when you are on desktop.
You are less secure though, but its worth it to me.
Honestly a big debate, so it really depends on your threat model. Lots of people even keep their totp seeds within their password manager which basically defeats 2fa imo, but it’s highly convenient. Personally I keep my totp seeds seperated in a sandboxed user profile.
I store my totp seeds in a separate, rarely used password manager, which then follows me on an “emergency USB” - hopefully something I won’t need to use at all
It only defeats 2FA from a standpoint of someone gaining access your PW manager. But for everything else like a service getting hacked and leaking your passwords for it, the 2FA will still do its job fine.
Depends on what is secure enough to you. For me that is secure enough but I know a ton of people out there who would say it’s not secure enough for them. So in the end it’s up to you. Think about the risks and make a decision.
In the case of Keepass, it is commonly said that it is best to have a database exclusively for your OTP.
For example, you have your passwords in a db called “My passwords” with an exclusive encryption password, and then another db called “My OTP’s” with its own encryption password, so if someone somehow get access to one, that person still won’t have access to the other, and therefore cannot enter your account.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
deleted by creator
Yuibkey authenticator app looks good. All tokens are in the hardkey.
Hardware keys for everything. Bitwarden for the rest.
My feelings are mixed regarding whether you should keep them on the same device… But I would strongly advise against you keeping them on the same app.
Well, the whole point of otp tokens/2fa, is to have a second login confirmation. Mostly on another device, like a phone.
Now maybe if you store your 2fa way on the same device, but locked away with a strong password, it may work, and could be safe enough.
But if it’s the same password as your device or another account, it isn’t that safe.
Aegis with the password in a YubiKey.
My password manager and I don’t know the password.
I might keep the in Bitwarden, then secured with hardware key.
I memorize the seed and calculate the next token in my head.
Passwords in KeePass, totp in Aegis.
My phone does have both, but they each have their own encryption.
I throw them all in Bitwarden which is protected with a long, unique password and a yubikey.
Same. Maximum comfort since Bitwarden autofills and puts the token in your clipboard, you dont have to change apps or need you smartphone when you are on desktop.
You are less secure though, but its worth it to me.
Honestly a big debate, so it really depends on your threat model. Lots of people even keep their totp seeds within their password manager which basically defeats 2fa imo, but it’s highly convenient. Personally I keep my totp seeds seperated in a sandboxed user profile.
I store my totp seeds in a separate, rarely used password manager, which then follows me on an “emergency USB” - hopefully something I won’t need to use at all
It only defeats 2FA from a standpoint of someone gaining access your PW manager. But for everything else like a service getting hacked and leaking your passwords for it, the 2FA will still do its job fine.
Depends on what is secure enough to you. For me that is secure enough but I know a ton of people out there who would say it’s not secure enough for them. So in the end it’s up to you. Think about the risks and make a decision.
In the case of Keepass, it is commonly said that it is best to have a database exclusively for your OTP.
For example, you have your passwords in a db called “My passwords” with an exclusive encryption password, and then another db called “My OTP’s” with its own encryption password, so if someone somehow get access to one, that person still won’t have access to the other, and therefore cannot enter your account.
Then use the same password for both for the sake of convenience.