Difference between revisions of "XMPP E2E Security"

Jump to navigation Jump to search
264 bytes added ,  09:37, 14 November 2018
no edit summary
 
(One intermediate revision by the same user not shown)
Line 5: Line 5:
== XEP-0384: OMEMO Encryption (Signal / Text Secure) ==
== XEP-0384: OMEMO Encryption (Signal / Text Secure) ==


'''Recommendation:''' Implement.
'''Recommendation:''' Implement if you need forward secrecy.


OMEMO is based on the Signal double ratchet and provides forward secrecy, compatibility with history retrieval for devices that are already part of the ratchet, and a number of other benefits over legacy encryption mechanisms. It has had an independent third party audit (see related links at bottom).
OMEMO is based on the Signal double ratchet and provides forward secrecy, compatibility with history retrieval for devices that are already part of the ratchet, and a number of other benefits over legacy encryption mechanisms. It has had an independent third party audit (see related links at bottom).
Line 112: Line 112:
= Abandoned and Legacy E2EE specifications =
= Abandoned and Legacy E2EE specifications =


Those specifications are very likely not relevant any more. They are listed here only for the sake of completeness.
Those specifications are very likely not relevant any more. They either gained no adoption or where replaced in favor of newer specifications. They are listed here only for the sake of completeness.


== draft-miller-xmpp-e2e ==
== draft-miller-xmpp-e2e ==
Line 122: Line 122:
https://xmpp.org/extensions/xep-0187.html
https://xmpp.org/extensions/xep-0187.html
https://xmpp.org/extensions/xep-0188.html
https://xmpp.org/extensions/xep-0188.html
== RFC 3923: End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP) ==
https://tools.ietf.org/html/rfc3923
165

edits

Navigation menu