193
submitted 1 year ago by neme@lemm.ee to c/privacyguides@lemmy.one
top 22 comments
sorted by: hot top controversial new old
[-] breadsmasher@lemmy.world 119 points 1 year ago

on desktop devices

Kinda should have been in the headline

[-] Tramort@programming.dev 44 points 1 year ago

It is a super important detail, but it's still unforgivable for an app that expects privacy to be part of its brand identity.

[-] breadsmasher@lemmy.world 8 points 1 year ago

unforgivable

yeah absolutely agreed

[-] brakebreaker101@lemmy.world 3 points 1 year ago

This is a big difference between privacy and security.

[-] Tramort@programming.dev 3 points 1 year ago

Agreed

But you can't have privacy without security, and any privacy brand must have security in their bones.

[-] claudiop@lemmy.world 7 points 1 year ago

You can't encrypt anything without a key. This is the key. If it wasn't in plaintext then it would be encrypted. Then you'd need a key for that. Where do you put it?

Phone OSs have mechanisms to solve this. Desktop ones do not.

But.. That's how encryption keys are stored.

[-] Evotech@lemmy.world 47 points 1 year ago

No your don't understand, you're supposed to encrypt the keys.

Then you encrypt that key

And then that key

Until it's all encrypted /s

[-] boredsquirrel@slrpnk.net 22 points 1 year ago* (last edited 1 year ago)

opportunistic TPM integration would be nice.

I.e. use the security chip of the device, if one is found. Otherwise use password.

OR use a Nitrokey etc, which can act as a secure device to store these keys too.

Take that, Windows. You dont need a builtin TPM if you can use a Nitrokey 3 with a secure element, externally.

[-] mashbooq@lemmy.world 50 points 1 year ago

This same "discovery" gets reported on once or twice a year; it's starting to feel like a FUD campaign rather than actual research

[-] potatopotato@sh.itjust.works 7 points 1 year ago* (last edited 1 year ago)

Yeah but it really shouldn't be that way. Just add a pin or something, it's way too easy for people to just grab devices or install malware to leak keys. The current standard for security is that everything is encrypted at rest regardless of whole disk encryption.

Signal is still better that most of the stuff out there but it's not above well intentioned criticism

[-] kakito69@sh.itjust.works 31 points 1 year ago

Not storing it in plaintext would require setting up some kind of password, right?

[-] boredsquirrel@slrpnk.net 15 points 1 year ago* (last edited 1 year ago)

Some way to encrypt the decryption key.

This could also mean TPM + Pin. Or using a Nitrokey, externally, which stores the password to decrypt the decryption key.

That is how user account unlocking (on GrapheneOS with Pixel phones) is done.

[-] joeldebruijn@lemmy.ml 29 points 1 year ago

While true I don't get why this is long known and also news at the same time.

For Signal Backup tools for example this isn't a bug but a feature and the only way to make long term archival of chats possible.

[-] boredsquirrel@slrpnk.net 4 points 1 year ago

You could archive chats encrypted too.

[-] joeldebruijn@lemmy.ml 2 points 1 year ago

Yep, decrypt ... export elsewhere to csv txt json ... encrypt

[-] eco_game@discuss.tchncs.de 29 points 1 year ago

I just read the full article, and I'm not even that concerned about storing the key in plaintext. I find the possibility of copying the files, and then being able to run the same session simultaneously a lot scarier.

[-] Blizzard@lemmy.zip 28 points 1 year ago

Should the encryption keys be... encrypted?

[-] RagingHungryPanda@lemm.ee 6 points 1 year ago
[-] JoeyJoeJoeJr@lemmy.ml 24 points 1 year ago

If your computer is compromised to the point someone can read the key, read words 2-5 again.

This is FUD. Even if Signal encrypted the local data, at the point someone can run a process on your system, there's nothing to stop the attacker from adding a modified version of the Signal app, updating your path, shortcuts, etc to point to the malicious version, and waiting for you to supply the pin/password. They can siphon the data off then.

Anyone with actual need for concern should probably only be using their phone anyway, because it cuts your attack surface by half (more than half if you have multiple computers), and you can expect to be in possession/control of your phone at all times, vs a computer that is often left unattended.

[-] otter@lemmy.ca 9 points 1 year ago

I've heard criticism of the desktop app before as well, maybe they'll finally rework it?

[-] DieserTypMatthias@lemmy.ml 1 points 1 year ago

Who is behind Stackdiary, btw?

this post was submitted on 06 Jul 2024
193 points (100.0% liked)

Privacy Guides

19760 readers
1 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.


You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...


Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!


This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.


Moderation Rules:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don't ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don't repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 2 years ago
MODERATORS