Privacy Guides
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.
- This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
- 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.
Additional Resources:
- EFF: Surveillance Self-Defense
- Consumer Reports Security Planner
- Jonah Aragon (YouTube)
- r/Privacy
- Big Ass Data Broker Opt-Out List
Hey, the oficial way are recovery codes. The idea is that you write them down and put them somewhere physically safe.
There is another way: You can register several second factor devices. Just scan the barcode multiple times before proceeding.
Basically any old phone, that you could store somewhere safe. I got two yubikeys that are in physically different locations.
Please note that every additional second factor increases your chances to recover access, but also the chance that someone gets access to them.
By using a password manager and second factor, you are already protecting yourself very well. Where you fall on the security vs convenience vs access triangle, you yourself probably know best.
I do Aegis for two factor and KeePass for passwords.
And of course offline backups. I like email aliases too, since it helps identify which sites you signed up for got breeched or is selling your email to get spam.
https://www.privacyguides.org/en/email/#additional-functionality_2
-Use your password manager for everything. 16-20 digit randomized passwords for each account. Change the password to everything you care about and put it in Bitwarden. Don't host your own instance of Bitwarden, unless you have really good backups. If things go wrong you're fucked.
-Your master password should be 5-7 words strung together. Brand names, uncommon words, etc. Avoid dictionary words except for 1 or 2. Use random brands, not something you own that can be socially engineered. Write it down, work on memorizing it for a week or so, then throw it away.
-Use 2FA on Bitwarden. If you can afford it, buy 2 yubikeys. One for your car keys, and one for a safe place at home. Add both to your account as your only 2FA method. This way there is zero possibility of an online attack. The only way your account could be compromised (outside of a software vulnerability) is a highly-targeted in-person attack, in which case, you have way bigger things to worry about. If you can't afford 2, than buy 1 and print out a Bitwarden 2FA backup code to store in a very safe place at home.
-This one is important: NEVER EVER USE SMS 2FA, too many things can go wrong (see: sim swapping). Pay the $10 a year for Bitwarden Premium and use the OTP 2FA codes. If a website doesn't have OTP (most do nowadays, it's usually labeled as the "authenticator app" option), than SMS is ok, just try to avoid it.
If you follow these instructions, I see no probable scenario in which you would have a breach caused by something on your end. A breach in Bitwarden (with it being FOSS and highly-audited, this is pretty unlikely) or, more likely, a breach in the service your account is using are the two scenarios you would realistically be breached.
Also, you're very very unlikely to be locked out of Bitwarden as long as you keep 1 yubikey and/or a printed backup code in a safe space at all times. If you end up with brain damage and forget your password, you'd be fucked I guess, but if you're that worried than write your password on paper in an obvious safe space. That definitely hurts your security though.
You could also fall for scams and/or social engineering, but that's a topic way beyond the scope of this post.
It's pretty important to remember that each device that you've installed the bitwarden client on has a local copy of your passwords, and you can always export your passwords too. So yeah, you need to have good backups in place if you self host vaultwarden, but I think it's one of the lower risk services to run in terms of actually losing your data.
Yes good point, I forgot about that.
I only know 2 passwords.
Bitwarden for all of my passwords. No OTP in bitwarden.
Bitwarden admin email's password is not in bitwarden, it's the only other password I know.
With all accounts supporting webauth I use yubikeys.
For accounts that don't support webauth, I use Aegis that's password secured with a static password on my yubikey so even I don't know that password.
If I lose all 3 of my yubikeys, them I'm SOL.
Right now I’m using Bitwarden as my primary password manager Before I switched, I had “all my eggs in one basket”, meaning my 2FA codes were stored alongside my passwords. This is a BAD practice. For one, Bitwarden offers 2FA to secure your account and storing this 2FA code in that very same Bitwarden account is very dumb because once you’re logged out… well… that’s it. Use a 2FA app on your phone. I highly recommend Raivo for managing your 2FA codes on iOS, not sure about Android. Using an app like this compounds your security because someone would have to have physical access to your device AND be able to access the codes on said device (Raivo offers takes pretty strong security measures) AND know your password/have access to your Bitwarden account. Raivo also offers you to export these codes in an encrypted zip file should you wish to back up to cloud storage or directly to your computer (depending on what OS your computer is, it might prove to be challenging moving this file from your phone) I hope this helps! Please ask me any questions if you have them. I’d be more than happy to answer them
My personal opinion on totp is that it's better to store them in bitwarden than to not use them at all, especially if your password is good and you've enforced two factor for registering a new device to bitwarden. It's definitely not the best way, but a lot more people can be convinced to right click and paste in an otp code over authenticating to a device, a totp app, and manually typing it in.
Keep backups of all things in a manual fashion.
Bitwarden is fine. BUt have a couple MFA options, including a set of printed recovery codes in a desk/safe etc.
Personally I use Google Authenticator TOTP (and not the version that syncs it to the cloud.). Instead I have a backup phone I keep in a fireproof safe and that also has a set of the codes. (Just do the "transfer" operation but at the end choose not to delete the codes from the original phone and boom you have TOTP on 2 devices.
I also use a Yubikey here and there, but only when I am physically a home (Its a PITA to move around).
Finally I have recovery/One time codes saved and printed. Just in case all else fails.
For any services that REQUIRE you to use SMS mfa, I go with something like google voice. If they block GV numbers, then i generally bail out of using the service...This especially includes banks.
The goal is
- No one MFA loss (Ie: phone stolen) will lose access to all accounts.
- An ability to recover even if all phones are lost.
- No storing totp for anything important inside bitwarden.
Check out my post about printed recovery codes/passwords:
yeah. I think that's a good idea. Personally I just keep them in a simple safe that is effective, preferably fire rated to an extent or just somewhere offsite. Even a safety deposit box is a great option.
I even sometimes just keep them in an encrypted fileshare on my synology NAS that is backed up and encrypted. But thats just extra for a non-tech person. For someone like my parents etc I just tell them to print them and keep them in safe space you wont misplace them. Because ideally the phone and your backup phone or a yubikey should have the main versions of MFA authentication.
Usually the recovery codes are 6-8 numbers that are a one time use thing.
Otherwise, i literally dont know many of my passwords off hand. The only ones I do are FDE decryption codes, and maybe my computer login.
Thanks for sharing
I like using KeePass and just syncing the password file between devices. Nobody can get open the file without at least the master password (you can use a key file as well), and it does 2fa.
I wouldn't tell you it's the best option, but it works for me and sizeable amount of other people: stateless password manager. It is an app that will generate you password based on input: url and a single master password.
Using same parameters gives the same password. Passwords are not stored, you just generate one whenever you need it. It solves syncing issues and eliminates option of losing your vault/backups. Master password should be extra secure, because it is the main defense point.
For the implementation, you could make one yourself with scripts (scrypt + base64) or use open-source apps like LessPass.
I use KeePassXC. It allows me to have strong passwords; it supports 2FA; and I can backup the key databases.
Make sure to set up an emergency sheet (https://passwordbits.com/password-manager-emergency-sheet/) and have it available at one or multiple safe places.
Diceware and a notebook. Otherwise, yea, what everyone else said.