- cross-posted to:
- technology@lemmy.world
- cross-posted to:
- technology@lemmy.world
You must log in or register to comment.
The number of times WhatsApp crashes in GrapheneOS is so high. GrapheneOS exposes all memory corruption bugs due to it’s hardened memory allocator and memory tagging features.
No wonder WhatsApp is exploited just like that. I sometimes think if these bugs were built purposefully.
With a Meta service it’s better to presume the worst than to give them the benefit of the doubt.
…Although I also have crashing issues with Voyager on GrapheneOS, so it could just genuinely be programming errors.
Wait we’re pretending WhatsApp isn’t spyware now?
In India, they’re running literal ads on billboards and TV saying WhatsApp can’t read your messages
If I recall correctly, at least for non-group chats they do use end-to-end encryption. That being said, obviously there are some practical limitations on the impact if you think that WhatsApp would actively try to be malicious, since they’re also providing the client software and could hypothetically backdoor that.
kagis
According to this, they do use end-to-end encryption for group chats too.
Maybe I’m recalling some other service or a default setting or something. Some service had non-e2e-encrypted-group messages for at least some period of time.
