Probably?
Technology
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- 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.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
If the entire supply chain up to the software you're running to perform actual decryption is compromised, then the decrypted data is vulnerable. I mean, yeah? That's why we use open-source clients and check builds/use builds from separate source, so that the compromission of one actor does not compromise the whole chain. Server (if any) is managed by one entity and only manage access control + encrypted data, client from separate trusted source manage decryption, and the general safety of your whole system remain your responsibility.
Security requires a modicum of awareness and implication from the users, always. The only news here is that people apparently never consider supply chain attacks up until now?
Ya think?
Let's expand that specifically generic headline. ""You probably can't trust anything if it's been compromised". More extra non-news at eleven.
Anyone got a good suggestion for a self hosted option? Ideally one that has a good iOS app and a web interface.
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?
Yes and no. You can store them in a free cloud account, provided you have local copies; there's a risk your access to the cloud storage could be denied. A security risk is that they could harvest these databases, and decrypt them later.
I think your best bet, if you were to use free services, is to delete old databases from the cloud. Encrypt the new databases with the updated password manager and a new master password.
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.
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.