Why Nostr? What is Njump?
2024-10-22 20:01:18
in reply to

Erik van Straten on Nostr: npub1hnh3g…prrkt : wow, that's a lot of snake oil in the FB article that The Verge ...

: wow, that's a lot of snake oil in the FB article that The Verge refers to.

*THE* problem with consumers losing access to their phone (stolen, forgotten in the subway, dropped in the toilet etc.) is typically that *ALL* secrets are gone - except a screen unlock code, while *possibly* the user may remember the password of their iCloud or Google account (or may have access to a rescue code).

B.t.w., passkey synchronisation suffers from the same problem: asking people to remember one or more additional *strong* passwords is doomed to fail in too many cases; fortunately black magic comes to the rescue.

From https://engineering.fb.com/2024/10/22/security/ipls-privacy-preserving-storage-for-your-whatsapp-contacts/:

But losing your phone could mean losing your contact list as well. Traditionally, WhatsApp has lacked the ability to store your contact list in a way that can be easily and automatically restored in the event you lose it.
[...]
If you lose your phone, your contact list can be restored on a newly registered device.
[...]
Certain events [...] trigger the creation of a new cryptographic keypair that is associated with your phone number.


So al the military grade encryption, HSM's and Cloudflare supervision eventually depends on a PHONE NUMBER - with, in modern computer terms, a VERY limited number of possible combinations of digits.

And all that apart from the fact that phone numbers may be spoofed and "SIM-swapping" attacks happen to be a lot easier than most people are aware of.

What could possibly go wrong?

P.S. Of course I may be totally mistaken, for example because additional protections are in place. However, I do not see them mentioned in the FB article.

#WhatsApp #AddressBook #Contacts #Meta #Facebook #Cloudflare #HSM #SnakeOil #MilitaryGradeEncryption #WriteOnceReadMany #BlockChain #Transparency #Passkeys #Synchronisation #E2EE
Author Public Key
npub1yzfshvmugq4nd4jhwve7hhwqzvvt7g9g23sharz5f5wdvg65r92qhql3r7