Nemeski@lemm.ee to

Privacy Guides@lemmy.oneEnglish · 4 months ago

Signal under fire for storing encryption keys in plaintext

198

Signal under fire for storing encryption keys in plaintext

Nemeski@lemm.ee to

Privacy Guides@lemmy.oneEnglish · 4 months ago

Popular encrypted messaging app Signal is facing criticism over a security issue in its desktop application. Researchers and app users are raising

Chat

kakito69@sh.itjust.works
link
fedilink
English
arrow-up
32·
4 months ago
Not storing it in plaintext would require setting up some kind of password, right?
- boredsquirrel@slrpnk.net
  link
  fedilink
  English
  arrow-up
  15·
  edit-2
  4 months 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.

Privacy Guides@lemmy.one

privacyguides@lemmy.one

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one

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:

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:

We prefer posting about open-source software whenever possible.
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.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
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.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
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.
No misinformation: Extraordinary claims must be matched with evidence.
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.
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:

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

1 user / day
20 users / week
633 users / month
2.63K users / 6 months
75 local subscribers
16.7K subscribers
261 Posts
1.22K Comments
Modlog