moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-22 01:02:17 -05:00
Code Issues Releases Wiki Activity

1.3pre1

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@231 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2006-11-28 16:59:20 +00:00
parent 9598e79416
commit 3cc5b33e6f
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
xep-0027.xml
View File

@ -28,6 +28,12 @@
<url>http://www.xmpp.org/schemas/x-signed.xsd</url> <url>http://www.xmpp.org/schemas/x-signed.xsd</url>
</schemaloc> </schemaloc>
&temas; &temas;
<revision>
<version>1.3pre1</version>
<date>in progress, last updated 2006-11-28</date>
<initials>psa</initials>
<remark>Removed the unnecessary requirement that the presence status or message body must contain XML character data, since the empty string can be signed.</remark>
</revision>
<revision> <revision>
<version>1.2</version> <version>1.2</version>
<date>2004-03-08</date> <date>2004-03-08</date>
@ -64,12 +70,7 @@
<p>All operations described here are done with standard OpenPGP software such as <link url='http://www.gnupg.org/'>GnuPG</link>. All program output is US-ASCII armored output with the headers removed. This allows for easy transportation of the program output directly in the XML. All keys are exchanged using OpenPGP key servers, and usually are retrieved when a signed &PRESENCE; stanza is received (key retrieval does not happen in-band).</p> <p>All operations described here are done with standard OpenPGP software such as <link url='http://www.gnupg.org/'>GnuPG</link>. All program output is US-ASCII armored output with the headers removed. This allows for easy transportation of the program output directly in the XML. All keys are exchanged using OpenPGP key servers, and usually are retrieved when a signed &PRESENCE; stanza is received (key retrieval does not happen in-band).</p>
</section1> </section1>
<section1 topic='Signing' anchor='signing'> <section1 topic='Signing' anchor='signing'>
<p>Signing enables a sender to verify that they sent a certain block of text. In Jabber, signing uses the 'jabber:x:signed' namespace, and is primarily used with &PRESENCE;, but may also be used with &MESSAGE;. Because signing requires a block of text, it creates new restrictions on the &PRESENCE; and &MESSAGE; stanzas:</p> <p>Signing enables a sender to verify that they sent a certain block of text. In Jabber, signing uses the 'jabber:x:signed' namespace, and is primarily used with &PRESENCE;, but may also be used with &MESSAGE;. The text that is signed MAY be the empty string. When signing presence, the sender SHOULD sign the XML character data of the &lt;status&gt; element. The sender SHOULD sign presence using the private key whose KeyID corresponds to the public key to be used in encrypting messages (see below).</p>
<ul>
<li>A &PRESENCE; stanza MUST have a &lt;status&gt; element containing XML character data.</li>
<li>A &MESSAGE; stanza MUST have a &lt;body&gt; element containing XML character data.</li>
</ul>
<p>These requirements are necessary so that there is always common text to sign and verify against. When signing presence, the sender SHOULD sign the XML character data of the &lt;status&gt; element. The sender SHOULD sign presence using the private key whose KeyID corresponds to the public key to be used in encrypting messages (see below).</p>
<example caption='A signed presence stanza'> <example caption='A signed presence stanza'>
&lt;presence from='pgmillard@jabber.org/wj_dev2' to='jer@jabber.org'&gt; &lt;presence from='pgmillard@jabber.org/wj_dev2' to='jer@jabber.org'&gt;
&lt;status&gt;Online&lt;/status&gt; &lt;status&gt;Online&lt;/status&gt;