Privacy

32096 readers

706 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

RFC: Cross Platform Password Manager (lemmy.radio)

submitted 4 months ago by vk6flab@lemmy.radio to c/privacy@lemmy.ml

25 comments fedilink hide all child comments

How are you storing passwords and 2FA keys that proliferate across every conceivable online service these days?

What made you choose that solution and have you considered what would happen in life altering situations like, hardware failure, theft, fire, divorce, death?

If you're using an online solution, has it been hacked and how did that impact you?

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

[–] chip@feddit.rocks 3 points 4 months ago (1 children)

Piggybacking on the comment. I also use syncthing to sync my keepass containers. Have you encountered duplication of database files (e.g. filename-sync-conflict-*), and if so, how have you solved them? I simply merge the files through KeepassXC when it happens.

[–] thayer@lemmy.ca 4 points 4 months ago* (last edited 4 months ago)

That used to happen to us before we started using SyncThing (and before we had data plans on our phones).

By the time we migrated to it, we had a home server running 24/7 and this ensured that at least one device in the chain was always online, had the latest version of the database, and pushed it to other devices as they came online. Our phones also have data plans now, so things generally sync in realtime which helps avoid issues.

If you don't have at least one always-online device, I think the next easiest way to avoid sync conflicts is to modify the database from one designated device. That way even if a conflict does arise, you'll know which device is always correct.

For resolving the conflicts, I would open both databases, sort by modified, and review the latest changes in each.