E2E encrypted messaging on Instagram will no longer be supported after 8 May
https://help.instagram.com/491565145294150
#HackerNews #E2EEncryption #InstagramMessaging #PrivacyPolicy #SocialMediaNews #TechUpdate
E2E encrypted messaging on Instagram will no longer be supported after 8 May
https://help.instagram.com/491565145294150
#HackerNews #E2EEncryption #InstagramMessaging #PrivacyPolicy #SocialMediaNews #TechUpdate
Every app claims to be "private."
Most are lying.
How to tell the difference:
π© RED FLAG: Won't show you code
β
GREEN FLAG: Open source on GitHub
π© RED FLAG: No security audit
β
GREEN FLAG: Published audit from Trail of Bits/NCC Group/Cure53
π© RED FLAG: Just says "encrypted"
β
GREEN FLAG: Says "end-to-end encrypted"
You don't need to be technical. You need to know what questions to ask.
Full guide: https://snugg.social/en/blog/how-to-verify-encryption-claims
#Privacy #Security #OpenSource #E2EEncryption #PrivacyMatters
Platform privacy comparison:
Signal: 3 data points collected (phone#, account date, last connection)
WhatsApp: 11+ categories, all shared with Meta
Telegram: Most chats stored unencrypted
Discord: ZERO encryption
Choose wisely. Full breakdown: https://snugg.social/en/blog/encrypted-doesnt-mean-private
AMD: Microcode Signature Verification Vulnerability
"... security vulnerability in some AMD Zen-based CPUs. This vulnerability allows an adversary with local administrator privileges (ring 0 from outside a VM) to load malicious microcode patches."
https://github.com/google/security-research/security/advisories/GHSA-4xq7-4mgh-gp6w
This is exactly the attack against which #confidentialcomputing should protect us
And it won't, when the attacker has access to ring0 of the hardware. Everywhere you don't run yourself.