Matches in DBpedia 2015-10 for { ?s ?p "OMEMO is an proposed XMPP Extension Protocol (XEP) for secure multi-client end-to-end encryption.OMEMO leverages axolotl encryption to provide multi-end to multi-end encryption, allowing messages to be synchronized securely across multiple clients, even if some of them are offline.OMEMO is a recursive acronym for OMEMO Multi-End Message and Object Encryption.It is an open standard based on Axolotl and PEP.OMEMO offers future and forward Secrecy and deniability with message synchronization and offline delivery.The protocol was implemented by Andreas Straub as a Google Summer of Code Project on 2015.The project aimed at implementing axolotl-based multi-end to multi-end encryption in the Android XMPP client Conversations."@en }
Showing triples 1 to 2 of
2
with 100 triples per page.
- OMEMO_(encryption) abstract "OMEMO is an proposed XMPP Extension Protocol (XEP) for secure multi-client end-to-end encryption.OMEMO leverages axolotl encryption to provide multi-end to multi-end encryption, allowing messages to be synchronized securely across multiple clients, even if some of them are offline.OMEMO is a recursive acronym for OMEMO Multi-End Message and Object Encryption.It is an open standard based on Axolotl and PEP.OMEMO offers future and forward Secrecy and deniability with message synchronization and offline delivery.The protocol was implemented by Andreas Straub as a Google Summer of Code Project on 2015.The project aimed at implementing axolotl-based multi-end to multi-end encryption in the Android XMPP client Conversations.".
- OMEMO_(encryption) comment "OMEMO is an proposed XMPP Extension Protocol (XEP) for secure multi-client end-to-end encryption.OMEMO leverages axolotl encryption to provide multi-end to multi-end encryption, allowing messages to be synchronized securely across multiple clients, even if some of them are offline.OMEMO is a recursive acronym for OMEMO Multi-End Message and Object Encryption.It is an open standard based on Axolotl and PEP.OMEMO offers future and forward Secrecy and deniability with message synchronization and offline delivery.The protocol was implemented by Andreas Straub as a Google Summer of Code Project on 2015.The project aimed at implementing axolotl-based multi-end to multi-end encryption in the Android XMPP client Conversations.".