No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0250.xml 16KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230
  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM 'xep.ent'>
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>C2C Authentication Using TLS</title>
  10. <abstract>This document describes how to negotiate TLS extensions when using TLS for end-to-end XML streams between two clients. It covers X.509 certificates with an without CA, the use of OpenPGP, Shared Remote Passwords (SRP) and how to use one extension to bootstrap a trust relationship.</abstract>
  11. &LEGALNOTICE;
  12. <number>0250</number>
  13. <status>Deferred</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <approver>Council</approver>
  17. <dependencies>
  18. <spec>XMPP Core</spec>
  19. <spec>XEP-0189</spec>
  20. </dependencies>
  21. <supersedes/>
  22. <supersededby/>
  23. <shortname>NOT_YET_ASSIGNED</shortname>
  24. &dmeyer;
  25. <revision>
  26. <version>0.2</version>
  27. <date>2008-09-08</date>
  28. <initials>dm</initials>
  29. <remark><p>Use keyinfo from version 0.8 of XEP-0189.</p></remark>
  30. </revision>
  31. <revision>
  32. <version>0.1</version>
  33. <date>2008-09-03</date>
  34. <initials>psa</initials>
  35. <remark><p>Initial published version.</p></remark>
  36. </revision>
  37. <revision>
  38. <version>0.0.2</version>
  39. <date>2008-08-26</date>
  40. <initials>dm</initials>
  41. <remark>
  42. <ul>
  43. <li>Add extension probing</li>
  44. <li>Add xmlsig namespace for keys</li>
  45. <li>Change namespace to urn:xmpp:tmp:c2ctls</li>
  46. <li>Add note about future TLS extensions</li>
  47. </ul>
  48. </remark>
  49. </revision>
  50. <revision>
  51. <version>0.0.1</version>
  52. <date>2008-08-22</date>
  53. <initials>dm</initials>
  54. <remark><p>First draft.</p></remark>
  55. </revision>
  56. </header>
  57. <section1 topic='Introduction' anchor='intro'>
  58. <p>For secure client-to-client (C2C) communication the clients can use &xep0174; or &xep0247; to open a connection between the two clients. To open an XMPP connection &xep0246; defines a stream setup similar to the setup used by client-server communications. To secure the communication the extension defines the use of Transport Layer Security as defined in &rfc5246; for encryption and authentication. XEP-0246 suggest to use the OpenPGP TLS extension but does not specify how to negotiate if both peers support the extension and if they are able to verify the OpenPGP key. It makes no sense to use OpenPGP instead of X.509 certificates if there is also no trust on OpenPGP level. This document describes how to negotiate how to use TLS to exchange possible extensions and key fingerprints before the actual TLS handshake.</p>
  59. <p>After the TLS handshake <strong>both</strong> communication partners MUST be sure that they are communicating with the correct person without a man-in-the-middle.</p>
  60. </section1>
  61. <section1 topic='Supported TLS Handshake Mechanisms' anchor='reqs'>
  62. <p>A client requires support for X.509 certificates or one or more TLS extension that can be used to verify the end-to-end character of the stream. The following list defines authentication mechanisms a client MAY support. The list depends on TLS extensions defined by the Transport Layer Security working group of the IETF. A future version of the document may include additional extension like Short Authentication String (SAS) or Kerberos. A client MUST ignore XML stanzas defining an authentication method it does not understand.</p>
  63. <section2 topic='X.509 Certificate'>
  64. <p>The classic usage of TLS is done with X.509 certificates. The certificate is the end of a certificate chain. A certificate should be either signed by another certificate from a third party or a well known certification authority installed on the client machine. In an enterprise scenario all client would be signed by a certificate from the company making it possible for all clients to verify the identity of the other.</p>
  65. <p>Getting a signed certificate is a complex and expensive task unsuitable for normal users. It also raises the question why a client should trust a CA its user does not know. Instead they create a self-signed certificate. The certificate is signed by itself and can not be verified through a certificate chain. To use these certificates in a real scenario the user must know the fingerprint of the peer certificate to verify it. But comparing fingerprints is not very userfriendly and the user may not have the fingerprint before starting the communication.</p>
  66. </section2>
  67. <section2 topic='OpenPGP Key'>
  68. <p>Instead of relying on a certificate chain the users may rely on a web-of-trust as defined by &rfc4880;. The TLS extension "OpenPGP Keys for Transport Layer Security" (&rfc5081;) describes how to use OpenPGP keys in the TLS handshake. If users share a trusted friend who has signed both their keys they can open a secure connection based on that trust. If there is no trust relationship between the two peers, OpenPGP is as useless as self-signed certificates. The users can verify the fingerprint and communicate that fingerprint over a different medium (e.g. a real-life meeting), but the same problem that occurs with X.509 certificates exists: comparing fingerprints is far away from being userfriendly.</p>
  69. </section2>
  70. <section2 topic='Shared Secret'>
  71. <p>A third way to verify the identify of the peer is a shared secret. This secret could be exchanged on a personal meeting or could be described as riddle only the other person can answer before opening the c2c link. It is up to the user and a good user interface to make the secret exchange as painless as possible.</p>
  72. <p>This document uses the Secure Remote Password (SRP) extension from &rfc5054; when dealing with shared secrets and not the Pre-Shared Key Ciphersuites as defined in RFC4279. SRP allows the users to choose a much smaller password and it still verifies both clients to the other. The password (shared secret) is required by both to calculate the premaster secret which means both will notice if the peer is not who it should be. SRP requires a user name; since it is transmitted in plain text between client and server it has no value in this context. Both clients must use the same username for the calculations. For the TLS handshake using SRP both clients MUST use the bare JID of the initiator as username.</p>
  73. </section2>
  74. </section1>
  75. <section1 topic='Protocol'>
  76. <section2 topic='Extension Negotiation'>
  77. <p>The main problem is what TLS extension to choose. It makes no sense to use OpenPGP if the clients have no trust-relationship or SRP if the users did not exchange a secret. To resolve this problem a client describes its extension in an offer to the peer. The offer lists all supported authentication methods including additional parameter like the certificate that will be used. &xep0189; can be used to look-up the keys or the client can look in its OpenPGP keyring. A client could also know a certificate or password from an earlier connection. The following example contains the X.509 certificate and the OpenPGP key from the examples in XEP-0189.</p>
  78. <example caption='Client Offer Supporting X.509, OpenPGP and SRP'><![CDATA[
  79. <offer xmlns='urn:xmpp:tmp:c2ctls'>
  80. <keyinfo xmlns='urn:xmpp:tmp:pubkey'>
  81. <name>428b1358a286430f628da23fb33ddaf6e474f5c5</name>
  82. </keyinfo>
  83. <keyinfo xmlns='urn:xmpp:tmp:pubkey'>
  84. <name>89d099a3428481cc63fe3fa44e7df2d002b4ce44</name>
  85. </keyinfo>
  86. <srp/>
  87. </offer>
  88. ]]></example>
  89. <p>Note: the keyinfo only contains the name and not the public key itself. If the peer does not know the key, it can not determine if it is an X.509 certificate or OpenPGP key. This does not matter because if the client does not know the key, it can not use it for secure communication.</p>
  90. <p>If both clients know the offer of the other, they can determine what method to use to complete the TLS handshake without an error. Note: this information will be exchanged over an insecure communication channel and may be forged. If the information is altered it will be detected when doing the TLS handshake.</p>
  91. </section2>
  92. <section2 topic='Extension Probing'>
  93. <p>I client MAY want to know the supported extensions of the peer before opening the client-to-client stream. For serverless messaging this is not possible but for server based communication a client can exchange offers with the peer without using Jingle to open a client-to-client stream. The methods the peer supports depend on additional information from the client. Depending on the X.509 certificate of the client the peer may not support this extension because it can not verify the certificate. To receive the offer from the peer the client sends an IQ stanza with its own offer.</p>
  94. <example caption='Client Sends Extension Probing IQ'><![CDATA[
  95. <iq type='get'
  96. from='romeo@montague.net/b345687ba7607d3ddf401a0257464843a0a1c0b7'
  97. to='juliet@capulet.com/da39a3ee5e6b4b0d3255bfef95601890afd80709'
  98. id='info'>
  99. <offer xmlns='urn:xmpp:tmp:c2ctls'>
  100. <keyinfo xmlns='urn:xmpp:tmp:pubkey'>
  101. <name>RomeoX509CertificateHash</name>
  102. </keyinfo>
  103. <keyinfo xmlns='urn:xmpp:tmp:pubkey'>
  104. <name>RomeoOpenPGPFingerprint</name>
  105. </keyinfo>
  106. <srp/>
  107. </offer>
  108. </iq>
  109. ]]></example>
  110. <p>The receiver sends its offer back to the client. It MUST only send the keyinfo elements that match a keyinfo of the offer. E.g. if the responder does not find an X.509 certificate it can verify in the offer it MUST NOT send its own X.509 certificate. In the following example the receiver supports SRP and X.509. OpenPGP is either not supported or skipped because the key can not be verified.</p>
  111. <example caption='Peer Sends Extension Probing Result'><![CDATA[
  112. <iq type='result'
  113. from='juliet@capulet.com/da39a3ee5e6b4b0d3255bfef95601890afd80709'
  114. to='romeo@montague.net/b345687ba7607d3ddf401a0257464843a0a1c0b7'
  115. id='info'>
  116. <offer xmlns='urn:xmpp:tmp:c2ctls'>
  117. <keyinfo xmlns='urn:xmpp:tmp:pubkey'>
  118. <name>JulietX509CertificateHash</name>
  119. </keyinfo>
  120. <srp/>
  121. </offer>
  122. </iq>
  123. ]]></example>
  124. <p>A client MAY support X.509 certificates it can not verify to be verified later. In that case it adds the authentication method &lt;insecure&gt;. In the following example the receiver supports SRP and X.509, but can not verify the certificate from the offer.</p>
  125. <example caption='Peer Sends Extension Probing Result'><![CDATA[
  126. <iq type='result'
  127. from='juliet@capulet.com/da39a3ee5e6b4b0d3255bfef95601890afd80709'
  128. to='romeo@montague.net/b345687ba7607d3ddf401a0257464843a0a1c0b7'
  129. id='info'>
  130. <offer xmlns='urn:xmpp:tmp:c2ctls'>
  131. <insecure/>
  132. <srp/>
  133. </offer>
  134. </iq>
  135. ]]></example>
  136. </section2>
  137. <section2 topic='STARTTLS Enhancements' anchor='starttls'>
  138. <p>The offer information described above will be embedded into the XML based part of the STARTTLS handshake described in the XMPP core.</p>
  139. <section3 topic='TLS Stream Feature'>
  140. <p>The recipient in the role of the XMPP server is the first one active in the XMPP TLS handshake. It offers the STARTTLS feature to the client. Instead of just offering the feature, it also SHOULD describe what TLS extensions it supports and what keys to expect. In the following example the recipient supports all possible identification mechanisms describe before.</p>
  141. <example caption='Recipient Sends Stream Features'><![CDATA[
  142. <stream:features>
  143. <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
  144. <required/>
  145. <offer xmlns='urn:xmpp:tmp:c2ctls'>
  146. <keyinfo xmlns='urn:xmpp:tmp:pubkey'>
  147. <name>RecipientX509CertificateHash</name>
  148. </keyinfo>
  149. <keyinfo xmlns='urn:xmpp:tmp:pubkey'>
  150. <name>RecipientOpenPGPFingerprint</name>
  151. </keyinfo>
  152. <srp/>
  153. </offer>
  154. </starttls>
  155. </stream:features>
  156. ]]></example>
  157. <p>If the recipient does not supply this additional information it is assumed that it does not support this extension and the TLS handshake continues as described in the XMPP core. If and how the users trust each other in that case is out of the scope of this document.</p>
  158. </section3>
  159. <section3 topic='Choosing the STARTTLS Feature'>
  160. <p>When the initiator starts the TLS feature it also enhances the STARTTLS with its supported extensions and additional key information based on the recipient's offer. In the following example the initiator can only verify one keyinfo. It also supports SRP.</p>
  161. <example caption='Initiator Starts TLS Feature'><![CDATA[
  162. <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
  163. <offer xmlns='urn:xmpp:tmp:c2ctls'>
  164. <keyinfo xmlns='urn:xmpp:tmp:pubkey'>
  165. <name>InitiatorX509CertificateHash</name>
  166. </keyinfo>
  167. <srp/>
  168. </offer>
  169. </starttls>
  170. ]]></example>
  171. <p>Similar to the feature announcement, if the initiator does not add an offer the recipient MUST assume the initiator does not support this XMPP extension and continue normal TLS handshake and hope it will work.</p>
  172. </section3>
  173. <section3 topic='Accepting STARTTLS'>
  174. <p>The next step for an recipient is to send an proceed message so the initiator can start with the TLS handshake. At this point the recipient knows what certificates or OpenPGP keys to expect from the peer and what the peer supports. The method that the initiator SHOULD use is added to the proceed.</p>
  175. <example caption='Recipient Accepts TLS'><![CDATA[
  176. <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
  177. <offer xmlns='urn:xmpp:tmp:c2ctls'>
  178. <srp/>
  179. </offer>
  180. </proceed>
  181. ]]></example>
  182. <p>The initiator now starts the TLS handshake.</p>
  183. <p>If only SRP is possible the client should ask the user if they exchanged a shared secret. If this is not the case no suitable methods are left and the recipient MUST sends a failure and close the stream.</p>
  184. <example caption='Recipient Aborts TLS'><![CDATA[
  185. <failure xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
  186. </stream:stream>
  187. ]]></example>
  188. </section3>
  189. </section2>
  190. </section1>
  191. <section1 topic='Bootstrapping Trust'>
  192. <p>After the c2c connection is secure the clients MAY use this secure and trusted connection to update their information on each other. Using XEP-0189 "Requesting Public Keys Directly From Another Entity" or "Sending Public Keys Directly To Another Entity" they can bootstrap a different mechanisms for the next time. A SRP-based connection can bootstrap the trust of a self-signed certificate which will used the next time these two clients connect to each other. It can also be used to automatically sign an OpenPGP key with a minimum level of trust.</p>
  193. </section1>
  194. <section1 topic='Usability Considerations' anchor='user'>
  195. <p>Usability Considerations will be provided in a future version of this document.</p>
  196. </section1>
  197. <section1 topic='Implementation Notes' anchor='impl'>
  198. <p>It is RECOMMENDED to always create a self-signed X.509 certificate for a client. It is of less value than an OpenPGP key also used by other applications and connected to a web-of-trust. It MAY also be stored on the users PC unencrypted like the XMPP password. This makes it possible to open secure communications without entering the OpenPGP password or the shared secret. Of cause, storing the X.509 certificate in plain text reduces the security. It all depends on how much the user trusts the PC.</p>
  199. </section1>
  200. <section1 topic='Security Considerations' anchor='security'>
  201. <p>Additional security considerations will be provided in a later version of this document.</p>
  202. </section1>
  203. <section1 topic='IANA Considerations' anchor='iana'>
  204. <p>This document requires no interaction with &IANA;.</p>
  205. </section1>
  206. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  207. <p>XMPP Registrar considerations will be provided in a later version of
  208. this document.</p>
  209. </section1>
  210. <section1 topic='Acknowledgements'>
  211. <p>
  212. The author would like to thank Eric Rescorla for suggesting TLS-SRP and
  213. others on the xmpp-security mailing list for the discussion.
  214. </p>
  215. </section1>
  216. <section1 topic='XML Schema' anchor='schema'>
  217. <p>The XML schema will be provided in a later version of this document.</p>
  218. </section1>
  219. </xep>