A privacy flaw in WhatsApp, an instant messenger with over 2 billion users worldwide, is being exploited by attackers to bypass the app’s “View once” feature and view messages again.

18 points

Not surprised since “view once” doesn’t actually exist on a computer you have control over

permalink
report
reply
4 points

Indeed, it should be clear to everybody that a motivated actor could record the view-once message, if nothing else by taking a picture of the screen with another device.

They are still useful to convey (in a rather strong way) the intention of keeping the message off-the-record, and to avoid the risk of a third party reading it e.g. by stealing the phone.

permalink
report
parent
reply

Yea, view-once features in apps are mostly an illusion that’s oversold.

We have something close to some sort of an actual view once thing at work… it involves controlled access into secure rooms with no windows, lawyers, NDAs, security takes your phone and whatnot kinda deal.

A self destructing message is better than nothing, but hardly a guarantee

permalink
report
parent
reply
7 points

Are you sure it’s a big and not a feature?

permalink
report
reply
1 point
*
Deleted by creator
permalink
report
reply

Privacy Guides

!privacyguides@lemmy.one

Create post

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:

Community stats

  • 594

    Monthly active users

  • 628

    Posts

  • 10K

    Comments