this post was submitted on 16 Feb 2026
212 points (89.8% liked)

Technology

81374 readers
4533 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

cross-posted from: https://infosec.pub/post/42164102

Researchers demo weaknesses affecting some of the most popular options Academics say they found a series of flaws affecting three popular password managers, all of which claim to protect user credentials in the event that their servers are compromised.…

you are viewing a single comment's thread
view the rest of the comments
[–] DeathByBigSad@sh.itjust.works 1 points 1 day ago* (last edited 1 day ago) (2 children)

Keepass, upload the database file to random free cloud accounts after making changes to the database.

This is foulproof as long as the end-user device doesn't get hacked, right?

Edit: Did I say something wrong? Why downvotes? Database file are encrypted, even if someone gets it, its encrypted and they don't have your password.

So its basically safe to upload your database. If you think I'm wrong then explain why I can't use free cloud accounts to store an encrypted file?

This is terrible advice, even if I assume you are also using a key-file on a removable usb. An attacker can brute force decrypt your db. There is no rate limiting when you literally have the database file, they could replicate it across thousands of servers each with dozens of cores, each core trying a dozen keyphrases per second. That's assuming a motivated attacker like a government or crypto scammers, but why open yourself to that possibility?

[–] oong3Eepa1ae1tahJozoosuu@lemmy.world 1 points 1 day ago (1 children)

Why would you do that? Just sync thr database with Syncthing and keep it locally on your devices. I'd never put my pw dB in a publicly available cloud online, even though it's encrypted.

[–] DeathByBigSad@sh.itjust.works 2 points 1 day ago* (last edited 1 day ago) (1 children)

For backup.

So all of my hard drives and devices are in the same house, if I was sleeping and and house caught on fire and I couldn't even get my phone in time (just a worst case example), then I lose all my passwords.

Cloud is my "offsite backup". Cuz where else would I put stuff?

Also: I though you could just safely upload encrypted files to Google Drive, why not a password database? It's just another encrypted file.

I see. For this scenario, I have another Syncthing server, which is on 24/7, responsible for offsite backups.

Ad encrypted files: true, but why expose them to a potential adversary? If there should be a flaw in the encryption (now or future) the other party already has access to the file.