Hacker News Reader

Comment by baby | Hacker News Reader

which sounds like it could be used to develop a federated protocol. I've heard there is an effort to do an RFC on the subject, but I'm not sure it uses the Signal protocols (for some reason), also there are two of them (I'm confused):

* https://tools.ietf.org/html/draft-barnes-mls-protocol-00

* https://tools.ietf.org/html/draft-omara-mls-architecture-01

View on HN

Using OMEMO on XMPP is a federated implementation of the Signal protocol. I believe Matrix' e2e encryption is also based on it.

I’m really hoping OMEMO makes it into Openfire (XMPP Server) and Adium (XMPP Client) sooner rather than later, we current use OTR but OMEMO is objectively superior in every way I can see.

In general, servers should have nothing to do with end-to-end encryption, except for not actively breaking it.

OMEMO in particular uses:

- Personal Eventing Protocol (PEP, XEP-0163) to transport key material; and

- core RFC3920/RFC6120 XMPP protocol to transport encrypted messages.

Both of which are already supported by Openfire [see JM-1122]. So, as far as I can tell, Openfire is fully capable of delivering OMEMO messages right now.

https://issues.igniterealtime.org/browse/JM-1122

[EDIT] For Adium OMEMO support, have a look at Lurch: https://github.com/shtrom/Lurch4Adium

I don't think Adium is doing much in terms of active development sadly.

Do you consider SMS a federated protocol?

https://silence.im/

SMS is federated, users of one providers can send messages to users of a different provider. Same with phone calls. Becoming a telephony provider probably takes a bit more investment than with some random Internet based service.

Reply on news.ycombinator.com