Opened 19 months ago

Last modified 8 months ago

#17528 new defect

Summarize Tor Messenger protocols

Reported by: sukhbir Owned by:
Priority: Medium Milestone:
Component: Applications/Tor Messenger Version:
Severity: Normal Keywords:
Cc: arlolra, boklm, special Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Here is start why we should do this:

<@arma> sukhe: is there a simple summary of the xmpp protocol somewhere, from the point of view of metadata?
<@arma> like, do my messages go through the center server too? and if i'm on one jabber server and the other person is on another, do the messages go through both of them? or is it only presence?
<@arma> sukhe: also, if i am talking to two people, using xmpp, does my tor messenger have one tcp connection, over tor, to the central server, and it carries both conversations?

Child Tickets

Change History (5)

comment:1 Changed 19 months ago by arma

  • Component changed from - Select a component to Tor Messenger

comment:2 Changed 19 months ago by arma

special points out that explaining who gets to see the contact list is also in-scope.

We could even imagine a table, like https://www.eff.org/secure-messaging-scorecard but with columns that reflect which parties get to access the metadata.

comment:3 Changed 19 months ago by arma

  • Cc special added

and I'm adding special to the cc, since he ought to want a table like this even more than you do, to explain why Ricochet has a better architecture than xmpp.

comment:5 Changed 8 months ago by arlolra

We did a bit of this at the recent meeting in Seattle (though not entirely this ticket's ask),
https://trac.torproject.org/projects/tor/wiki/org/meetings/2016SummerDevMeeting/Notes/Messaging#WhatmakesaTor-enabledMessengerToday

Note: See TracTickets for help on using tickets.