moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

Update the version number to 0.1 for the two XEP-0373 and XEP-0374

This commit is contained in:
Ash Ward 2016-05-10 15:48:52 +01:00
parent f907c8f63d
commit 70561049c7
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
xep-0373.xml
View File

@ -61,7 +61,7 @@ Standards Foundation.</permissions>
<jid>valodim@stratum0.org</jid>
</author>
<revision>
<version>0.0.2</version>
<version>0.1</version>
<date>2016-05-10</date>
<initials>XEP Editor (ssw)</initials>
<remark><p>Initial published version approved by the XMPP Council.</p></remark>
@ -172,7 +172,7 @@ Standards Foundation.</permissions>
(Ed.). Springer-Verlag, London, UK, UK, 83-107. &lt;<link
url='https://www.iacr.org/archive/eurocrypt2002/23320080/adr.pdf'>https://www.iacr.org/archive/eurocrypt2002/23320080/adr.pdf</link>&gt;</note>.
The XMPP address found in the 'to' element's 'jid' attribute
SHOULD be without Resourcepart (i.e. a bare JID). A &sign; content
SHOULD be without Resourcepart (i.e., a bare JID). A &sign; content
element may not carry a 'to' attribute. The 'time' element MUST
have a 'stamp' attribute which contains the timestamp when the
OpenPGP content element was signed and/or encrypted in the

8
xep-0374.xml
View File

@ -55,7 +55,7 @@ Standards Foundation.</permissions>
<jid>valodim@stratum0.org</jid>
</author>
<revision>
<version>0.0.2</version>
<version>0.1</version>
<date>2016-05-10</date>
<initials>XEP Editor (ssw)</initials>
<remark><p>Initial published version approved by the XMPP Council.</p></remark>
@ -73,12 +73,12 @@ Standards Foundation.</permissions>
<p>This XMPP extension protocol specifies a profile of &xep0373; for OpenPGP
secured Instant Messaging (IM).</p>
<p>Unlike similar XEPs, e.g. OMEMO, this XEP <em>does not</em>
<p>Unlike similar XEPs, e.g., OMEMO, this XEP <em>does not</em>
provide Forward Secrecy (FS), but as an advantage in return, allows
users to read their archived conversations (respectively their
encrypted data) later on. Of course, only as long as they still
possess the according secret key. FS and being able to decrypt
archived messages are mutually exclusive, i.e. one can not have
archived messages are mutually exclusive, i.e., one can not have
both. The authors therefore consider this XEP complementary to
similar ones which also provide end-to-end encryption but with a
different feature set.</p>
@ -90,7 +90,7 @@ Standards Foundation.</permissions>
<section2 topic='Discovering Support' anchor='disco'>
<p>If an entity supports exchanging OpenPGP encrypted and signed
instant messages over XMPP, i.e. what is specified herein, it MUST
instant messages over XMPP, i.e., what is specified herein, it MUST
advertise that fact by announcing a &xep0030; feature of
'urn:xmpp:openpgp:im:0'. It thus includes this feature in response
to a service discovery request.</p>