Changes between Version 2 and Version 3 of EndToEndXMPPCrypto


Ignore:
Timestamp:
01/25/14 19:47:31 (5 years ago)
Author:
elb
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • EndToEndXMPPCrypto

    v2 v3  
    2525 There may be additional room for integration here; for example, authentication of the basic presence information is also desirable, but I do not consider it a strict requirement.
    2626 * '''Streamlined one-on-one Chat.'''  An equivalent protocol to the XMPP simple <message> stanza with a cleartext <body>, only encrypted and authenticated.  The point of this protocol is to minimize overhead for typical one-on-one chat, for the benefit of mobile and bandwidth- or computationally-constrained clients.
     27 * '''Arbitrary protected stanzas.'''  A method should be provided for protecting arbitrary end-to-end XMPP stanzas, either with only authentication or with both authentication and encryption.  An example mechanism supporting this point would be an e2e encrypted data stanza simply containing a standard XMPP stanza that has been encrypted and authenticated that is unwrapped at the receiving client and then processed as if it had been in place of the encrypted stanza.  Existing standards and best practices for encrypting partial XML documents should be consulted.
     28 * '''A plurality of key authentication mechanisms.'''  The public key exchange mechanism should allow for multiple disparate authentication methods to be communicated.  For example, an S/MIME signature using a PKI x.509 certificate and a GPG signature of the same key material might be provided, along side whatever native signing protocol is used.  These authentication mechanisms should be readily extensible and have enough structure that useful mechanisms can be clearly defined.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!