Privacy

32103 readers

693 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

How you all prevent Password/OTP/TOTP deadlocks? (programming.dev)

submitted 7 months ago by alexdeathway@programming.dev to c/privacy@lemmy.ml

34 comments fedilink hide all child comments

I have read quite a few posts about preventing account password takeover from various malicious ways, and many OPSEC measures are there to prevent it from happening.

Consider a case where you face a total blackout or technical failure. Now, you need to log in to your password manager, which requires either OTP on email or TOTP. You don't have access to the TOTP app because the backup is stored in cloud storage, whose email login also requires OTP.

How would you prevent such from happening?I haven't found a satisfactory solution or explanation for that yet.

you are viewing a single comment's thread
view the rest of the comments

[–] veroxii@aussie.zone 1 points 7 months ago (1 children)

I thought KeePass files are strongly encrypted. How are they the weakest link if you use a proper pass phrase?

[–] mp3@lemmy.ca 5 points 7 months ago* (last edited 7 months ago) (1 children)

A strong and unique passphrase is indeed really important here, but you need to keep in mind that once the kdbx file is in the attacker's hand, that's the only thing that keep them out.

There's no 2FA, and no throttling on the bruteforce process. So it's really important to use a strong password there to avoid it being the weakest link.

[–] catloaf@lemm.ee 3 points 7 months ago (1 children)

You can kind of do MFA on the database. You can require a key, which can be very long and complex, and you can store it on a USB drive. You might be able to use a key stored on a yubikey or something too, I haven't tried it. It probably depends on which KeePass variant you're using.

[–] sntx@lemm.ee 1 points 7 months ago (1 children)

I use KeePass with three factors:

The password
A keyfile I distribute out of band between all hosts that should be able to open the database
A set of Hardware Keys supporting challange-response

Works really well IMO. I use KeePassXC on Linux and KeePass2Android on Android.

[–] mp3@lemmy.ca 2 points 7 months ago (1 children)

I suppose they all use the same challenge-response key?

[–] sntx@lemm.ee 2 points 7 months ago

Yes, unfortunately they need to atm.