Privacy

39870 readers

510 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

[ANSWERED] Should i use KeePass* instead of Proton Pass, for privacy? (lemmy.dbzer0.com)

submitted 1 day ago* (last edited 17 hours ago) by somerandomperson@lemmy.dbzer0.com to c/privacy@lemmy.ml

56 comments fedilink hide all child comments

One downside is that i'll have no more passkeys. The vault syncing, i can do via SyncThing.

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

[–] slackness@lemmy.ml 1 points 18 hours ago (1 children)

You can't talk about E2EE on a closed source client.

[–] rumba@lemmy.zip 1 points 18 hours ago (1 children)

What is this fight club? /s

You could totally talk about E2EE if the client was SA/Electron. If the blob is just getting transferred and stored and the passphrase is never transferred, that's E2EE.

Come to think of it, if they throw in extra keys when you make your blob, it's still E2EE, even if they have a key for it. Perhaps we need to think differently about E2EE being then end all.