3 ms·
Sorry for spreading it if it is FUD indeed (cannot edit anymore). I'll concede that I am not skilled or motivated enough to verify all that is asserted there; I
by nicoco 4y ago
Sorry for spreading it if it is FUD indeed (cannot edit anymore). I'll concede that I am not skilled or motivated enough to verify all that is asserted there; I think my other points about E2EE still stand, don't they?
There is a lot of FUD about XMPP in comments on HN, and I feel bad for (potentially) doing the same thing about matrix, this was not my goal.
- Arathorn 4y ago> Sorry for spreading it if it is FUD indeed np; thanks for listening :) > I think my other points about E2EE still stand, don't they? I think the question is whether the recipient should be able to move message keys between their devices so they can decrypt messages from the server when they log in on a new device. Given the recipient already has the plaintext of the messages, they can obviously copy the plaintext to the new device (as Signal and Wire do, for instance). Alternatively, if the recipient has the message keys (as in Matrix), they can copy those to the new device and use them to redecrypt the history off the server. This gives the same end result, but with less data being transferred between the clients. It doesn’t violate any E2EE; it’s just the recipient chosing to process their history as they like.
- singpolyma3 4y agoOMEMO let's you move keys to a new device no problem, if you buy a new phone and will no longer use the old one for instance.