Re: Proposed XMPP Extension: End-to-End Encrypted Contacts Metadata
Goffi <[email protected]>
| Newsgroups | gmane.network.jabber.standards-jig |
|---|---|
| Message-ID | <3675029.iIbC2pHGDl@tazar3> |
Le mardi 20 janvier 2026, 19:45:35 heure normale d’Europe centrale Thilo Molitor a écrit : > To be honest, I don't understand the "encrypted roster" discussion. > Even if the server does not see the roster at all, it is able to fully infer > which jids are part of a user's "roster" by just checking the PubSub > subscriptions and fetches of that user. > > Isn't an "encrypted roster" implemented this way just a farce? > Or do I miss something important here? > > -tmolitor The JID is not visible, it's a random ID in the pubsub items, and the fetches are done whenever client want to sync. There is a single node to subscribe, you can't get any information from that, beside a very approximate size of the roster, and the <reserved> element is there to make it muddy. The server can know who you are communicating with by checking "from" and "to" from message (until we have something like sealed sender), or checking PEP requests (for OMEMO for instance), but the goal here is to hide the sensitive metadata (name, and groups, possibly other things). This is a first step toward metadata reduction. The server can vaguely guess the relations of the entity, but it has less information than before. Other steps such as sealed sender will be discussed (notably at the incoming summit). Best, Goffi _______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEsNZvWyEnjW9SVudbKqmcu6xuKwwFAmlv11kACgkQKqmcu6xu KwzTogf9FeAhoV2TXxx7ipQ5qZdRN2wGlf+KgEzHSeDioWUWJX68jwYax8fJsbCe Zx3uTSCU1NxZ9l1d0uLqEiZwz9T6S0cZE4EN6pDlIWcID0+wfoZTya8Y6cyrRkuh UzuRkWyRmSst93B1PLbifXpkSrGe3tUDRy9FBfQ5KJ+bVoIyCBTR9wTJ1VUb5ZYy Bh7AvmA0yNoGNHbFevAntiADR/bURmYZzsEGMAZfRv/kuHQ+Idl/aVJojpgj/IcO rXSwdTsm6knAQPfEpXYpGkK+Wy+6eBGE8h6jAaeKgEF1m0iHBeDoBqu2gBy9lHM7 ahPZ5tCRQZfybjvy1LyHCJRQpZl3EQ== =uVe8 -----END PGP SIGNATURE-----