From bddc7bd04a65988a20dd8416d91899a78f7a268b Mon Sep 17 00:00:00 2001 From: Emmanuel Gil Peyrot Date: Sun, 28 Aug 2016 16:05:02 +0100 Subject: [PATCH] Explicit Message Encryption ProtoXEP: Add a 0.0.2 version MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Made the 'name' attribute optional for existing mechanisms. - Added a remark about the possibility to hide encrypted messages following user input. - Made explicit that this protocol affects any encryption mechanism, present or future, not only those listed here. - Display the namespace of the encryption mechanism in the default messages. - Remove the second example message, which didn’t add any useful information. --- inbox/eme.xml | 53 +++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 39 insertions(+), 14 deletions(-) diff --git a/inbox/eme.xml b/inbox/eme.xml index 14664fbb..2edd02d4 100644 --- a/inbox/eme.xml +++ b/inbox/eme.xml @@ -29,6 +29,20 @@ linkmauve@linkmauve.fr linkmauve@linkmauve.fr + + 0.0.2 + 2016-08-28 + egp +
    +
  • Made the 'name' attribute optional for existing mechanisms.
    • +
  • Added a remark about the possibility to hide encrypted messages + following user input.
    • +
  • Made explicit that this protocol affects any encryption mechanism, + present or future, not only those listed here.
    • +
  • Display the namespace of the encryption mechanism in the default + messages.
    • +
+ 0.0.1 2016-08-14 @@ -77,7 +91,6 @@ id='secret1'> ?OTR?v23?... ]]> @@ -86,7 +99,8 @@ display that the message was encrypted but that it is not able to decrypt it instead of displaying the body, for example:

-

🔒 This message was encrypted with OTR and could not be decrypted.

+

🔒 This message was encrypted with OTR (urn:xmpp:otr:0) and could not be + decrypted.

Juliet may then communicate to Romeo that she was unable to receive his @@ -104,7 +118,6 @@ This message is encrypted with OpenPGP for XMPP. ]]> @@ -112,17 +125,19 @@

Upon receiving this message, Juliet’s current client prompts her to enable a plugin, or even do it on its own, possible representations include:

-

🔒 This message was encrypted with OpenPGP for XMPP, click - here to enable this plugin.

-
-
-

🔒 This message was encrypted with OpenPGP for XMPP, downloading and - installing an appropriate plugin, your message will be displayed - shortly.

+

🔒 This message was encrypted with OpenPGP for XMPP + (urn:xmpp:openpgp:0), click here to enable this + plugin.

+

Any encryption mechanism using message as a transport is a candidate, and + MAY have a 'name' attribute to help the receiving client display it to the + user, in case this client doesn’t understand its namespace yet. A 'name' + attribute SHOULD NOT be included for the protocols listed herein, and + SHOULD be ignored by a receiving client:

+ @@ -156,7 +171,7 @@

If an entity supports the Encrypted Message Extension protocol, it MUST report that by including a &xep0030; feature of "urn:xmpp:eme:0" in response to disco#info requests:

- ]]> - +

A sender entity MAY include a 'name' attribute for any encryption + mechanism not listed in this specification, to help the receiving entity + present it to the user, but SHOULD NOT include one for the ones listed + here.

+

A receiving entity MUST NOT use the 'name' attribute if it is present and + they already have a name associated with it.

+

A receiving entity MAY not display anything in case an encrypted message + has been received, if the user agreed to that behaviour.

When a message is marked with an encryption tag and can not be decrypted, the body can safely be ignored and a localized message displayed instead.

+

If an entity includes a 'name' attribute, it should attempt to localise it + to the best of its abilities for the receiving client.

 @@ -216,7 +241,7 @@ -

This specification defines the following XML namespace:

+

This specification defines the following XML namespace:

  • 'urn:xmpp:eme:0'
@@ -241,8 +266,8 @@ - +
Name