diff --git a/inbox/ephemeral-messages.xml b/inbox/ephemeral-messages.xml new file mode 100644 index 00000000..26e95f29 --- /dev/null +++ b/inbox/ephemeral-messages.xml @@ -0,0 +1,209 @@ + + + +%ents; +]> + + +
+ Ephemeral Messages + This specification defines a protocol to send ephemeral messages over XMPP and synchronize timer value setting across devices. + &LEGALNOTICE; + xxxx + ProtoXEP + Standards Track + Standards + Council + + XMPP Core + XEP-0334 + XEP-0384 + + + + NOT_YET_ASSIGNED + + Alexander + Krotov + ilabdsf@gmail.com + + + 0.0.1 + 2018-04-10 + psa +

First draft.

 + +
+ +

Existing protocols deployed in XMPP networks offer forward secrecy both on the transport (TLS) and message (&xep0027; and &xep0384;) levels. Forward secrecy prevents recorded communications from being decrypted even if long term encryption keys are compromised by generating ephemeral keys and securely deleting them when they are no longer needed.

+ +

However, even though keys are deleted, message contents is retained both in server and client archives. While servers can be instructed with message hints (&xep0334;) not to store some messages in the archives (&xep0313;) or prevented from saving them in plain text by the use of end-to-end encryption, most XMPP clients still retain message content almost indefinitely. A device with an installed XMPP client that can be lost or stolen becomes the weakest link.

+ +

Unlike ephemeral keys, which have specified lifetimes, message contents cannot be removed immediately after being read. Users have to decide for how long they want to retain conversation contents. Verbally agreeing on the time interval and manually removing messages from all devices is cumbersome and error-prone.

+ +

This XEP defines a way to attach a timer value to messages which in order to specify for how long XMPP clients should store message contents. Besides that, it defines a way to synchronize common timer setting across all users of the conversation.

+ +

The specification does not depend on any encryption scheme and does not require encryption at all. It can be used with plaintext messages as long as users trust their servers to respect &xep0334;.

+ +

Other IM systems, such as Signal, Wickr, Wire and Telegram, already offer ephemeral messages. Signal offers timer synchronization feature for user groups and Telegram offers it for secret chats, which are limited to two users.

+ + + + + +
+
Explicit timer update
A message with an empty ephemeral tag, sent to update timer setting on all devices participating in a chat.
 +
Implicit timer update
A message with a non-empty ephemeral tag, treated as a timer update for the puprose of timer setting synchronization.
 +
+ + + +

If an entity supports ephemeral messages, it MUST advertise that fact in its responses to &xep0030; information (disco#info requests by returning a feature of &ephemeral;.

+ + + +]]> + + + + + +]]> +

An XMPP client SHOULD warn the user if not all recipients support ephemeral messages.

+

To avoid downgrade attack, an XMPP client MUST allow the user to force sending of ephemeral message even if no recipient has indicated support for them.

+ + +

To send an ephemeral message, an XMPP client places message contents into <ephemeral> tag with a <timer> attribute set to the number of seconds after which the message contents is to be securely deleted from the recipient device. XMPP client MUST include a <no-permanent-store/> hint (see &xep0334;), as any permanent storage of ephemeral message defeats its purpose.

+

Here is an example of sending a plaintext ephemeral message with a 24 hours (86400 seconds) timer value.

+ + + + TODO insert some message text + + + + This is an ephemeral message. + + + +]]> + + +

When user manually changes ephemeral message timer setting in an XMPP client, XMPP client SHOULD send an ephemeral message timer update.

+

Timer update message SHOULD be sent immediately. An XMPP client MAY choose to postpone sending a timer update, remember the current value and ignore implicit timer updates until either the user sends a message or an explicit timer update is received. It may be useful, for example, to avoid waking up wireless connection when user device has low battery.

+

A timer update is simply an ephemeral message without a body. However, for timer setting updates XMPP client SHOULD use <store> hint, to ensure that timer setting is updated properly on offline clients when they go online.

+ + + + +]]> + + +

An XMPP client receiving an message with an <ephemeral> tag SHOULD update the timer setting to the value of timer attribute. It MAY ignore implicit timer updates if it has postponed sending a timer update message, as described in Sending a Timer Setting Update section.

+

The rationale for updating the timer value upon receiving ephemeral messages with contents, in contrast to explicit ephemeral timer updates, is to make sure devices get synchronized eventually even if timer updates are lost. It may happen, for example, if some device stays offline longer than the lifetime of offline message storage (see &xep0160;).

+

After that, client moves the contents of <ephemeral> into the <message> and ignores any elements outside the <ephemeral>, such as <body> element intended for legacy clients.

+

The resulting message is processed as usual.

+ + +

OMEMO requires that messages are delivered in a sequence. If a message is missing, all the following messages cannot be decrypted and a new session has to be established. To prevent this kind of situation, additional steps are required to make sure ephemeral messages are not sent to clients that will ignore them because they do not support them.

+ +

An OMEMO-capable device implementing ephemeral messages MUST indicate support for ephemeral messages in its Bundle (see &xep0384;).

+ + + + + + + + + + + + +]]> + + +

When sending an ephemeral OMEMO message, XMPP client MUST NOT encrypt it for clients that did not indicate support for ephemeral messages explicitly.

+ + + +

While OMEMO in its current revision allows only the body to be encrypted, some other encryption schemes, such as &xep0374; allow to encrypt the <ephemeral> tag itself.

+

If such a scheme is used, an XMPP client SHOULD encrypt <ephemeral> tag instead of placing encrypted message into it.

+ + + +

Sender device MUST start the timer immediately after sending it, if Stream Management is not used (&xep0198;) or after receiving acknowledgement for <message> stanza, if Stream Management is available. This rule prevents the message from being deleted before it is successfully delivered to the server.

+ +

Device receiving a &xep0280; carbon copy MUST start the timer immediately.

+ +

Messages received from other JID MUST be stored in the database along with their timer value and timer SHOULD NOT start until the user reads a message. When the message is read by the user, for example by opening a chat window, an XMPP client starts a timer and MUST securely delete message contents from the device when the timer expires. An XMPP client SHOULD NOT display message contents outside the chat window, for example in system notifications. However, if it is displayed outside the chat window, for example when the last message for the contact is displayed in the roster window, an XMPP client MAY not start a timer until user explicitly opens the chat window.

+ + +

If encrypted ephemeral messages are used, timer setting may become unsynchronized for devices that can not decrypt ephemeral messages. For this reason, whenever user changes an encryption scheme, an XMPP client SHOULD send an send an explicit timer update.

+ + + +

XMPP client MAY translate the message "This is an ephemeral message." to other languages and include multiple <body> elements with different xml:lang attributes for legacy clients.

+ + +

Devices implementing this specification MUST securely delete messages. For example, if SQLite is used as a database, secure_delete pragma MUST be set to 1 explicitly.

+

An XMPP client MUST NOT let the message contents outside the application, even to display it in a system notification. It has led to privacy issues in existing IM software before.

+

Plaintext ephemeral messages should not be relied upon for privacy. Legacy clients may store messages as raw XML contents, including the <ephemeral> tag, in their databases. Messages may be sent to third parties accidentally, for example if one of the servers is configured to deliver message contents in push notifications (&xep0357;).

+ + +

This document requires no interaction with the Internet Assigned Numbers Authority (IANA).

+ + +

This specification defines the following XML namespaces:

+ +

Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.

+ + + + + + + + + The protocol documented by this schema is defined in + XEP-xxxx: http://www.xmpp.org/extensions/xep-xxxx.html + + + + + + + +]]> + + +

Thanks to Paul Schaub for the feedback incorporated into this specification.

+ + \ No newline at end of file