4 ms·

They can't just change the verification code, and it's not based on the fields of the contact card. You can think of it as a fingerprint for their iMessage publ

by thamer 3y ago

They can't just change the verification code, and it's not based on the fields of the contact card. You can think of it as a fingerprint for their iMessage public key, the one used to encrypt messages end-to-end. If the key with which your phone encrypts iMessage payloads has changed, it indicates that the conversation is being intercepted. WhatsApp supports this too, see "Verify Security Code" on this page: https://faq.whatsapp.com/820124435853543 https://faq.whatsapp.com/820124435853543 So does Signal: https://support.signal.org/hc/en-us/articles/360007060632-What-is-a-safety-number-and-why-do-I-see-that-it-changed- https://support.signal.org/hc/en-us/articles/360007060632-Wh... So does Telegram: https://telegram.org/faq#q-what-is-this-39encryption-key-39-thing https://telegram.org/faq#q-what-is-this-39encryption-key-39-...

grgar 3y ago
But the verification code is stored in the contact card, so the parent comment still stands. Anything that can access contacts, e.g. apps or iCloud (since Contacts are not part of Advanced Data Protection i.e. E2E encryption), can modify the verification code in the contact used by Messages for validation.
- brookst 3y ago
  Are you saying the iOS contacts API lets apps read and write the verification code? That seems like terrible design. What need would a 3P app have for that capability?
  - isodev 3y ago
    No, there is no way for apps to read and write this information.
- lilyball 3y ago
  According to https://security.apple.com/blog/imessage-contact-key-verification/ https://security.apple.com/blog/imessage-contact-key-verific..., the actual verified hash of the account key is stored in an end-to-end encrypted CloudKit container and merely linked to from the contact card.
  - _rs 3y ago
    Oh interesting, that is not at all clear based on the Contacts UI which shows it like any other field
    - blurrybird 3y ago
      That’s just good UI design. Make complex stuff look dead simple.
    - varenc 3y ago
      The iOS Contact APIs shouldn't allow modifying this. You can also try exporting the contact to a vCard .vcf file using the Share Contact button. I believe the iMessage key verification info won't be included. (But as you noted the most important thing is that it can't be modified)

by thamer 3y ago

grgar 3y ago

But the verification code is stored in the contact card, so the parent comment still stands. Anything that can access contacts, e.g. apps or iCloud (since Contacts are not part of Advanced Data Protection i.e. E2E encryption), can modify the verification code in the contact used by Messages for validation.

brookst 3y ago
Are you saying the iOS contacts API lets apps read and write the verification code? That seems like terrible design. What need would a 3P app have for that capability?
- isodev 3y ago
  No, there is no way for apps to read and write this information.
lilyball 3y ago
According to https://security.apple.com/blog/imessage-contact-key-verification/ https://security.apple.com/blog/imessage-contact-key-verific..., the actual verified hash of the account key is stored in an end-to-end encrypted CloudKit container and merely linked to from the contact card.
- _rs 3y ago
  Oh interesting, that is not at all clear based on the Contacts UI which shows it like any other field
  - blurrybird 3y ago
    That’s just good UI design. Make complex stuff look dead simple.
  - varenc 3y ago
    The iOS Contact APIs shouldn't allow modifying this. You can also try exporting the contact to a vCard .vcf file using the Share Contact button. I believe the iMessage key verification info won't be included. (But as you noted the most important thing is that it can't be modified)