Difference between revisions of "Stanza encryption"

Jump to navigation Jump to search
921 bytes added ,  12:51, 31 March 2019
no edit summary
Line 14: Line 14:


Most importantly though we need experience in this field in order to get a better understanding of what pitfalls exist, so lets JUST DO IT!
Most importantly though we need experience in this field in order to get a better understanding of what pitfalls exist, so lets JUST DO IT!
== Requirements ==
* IQ Stuff between two (online) devices. It would be nice to be able to establish some sort of longer standing session in that case
* Multi device message stuff.


== Related Work ==
== Related Work ==
Line 23: Line 28:


* [https://xmpp.org/extensions/xep-0246.html XEP-0246: End-to-End XML Streams]
* [https://xmpp.org/extensions/xep-0246.html XEP-0246: End-to-End XML Streams]
* [https://xmpp.org/extensions/inbox/jingle-xtls.html XEP-XXXX: XMPP Transport Layer Security]


=== Encryption Protocols ===
=== Encryption Protocols ===
Line 33: Line 40:


* [https://xmpp.org/extensions/xep-0116.html XEP-0116: Encrypted Session Negotiation]
* [https://xmpp.org/extensions/xep-0116.html XEP-0116: Encrypted Session Negotiation]
* [https://op-co.de/tmp/SEX.html Simple Encryption for XMPP]
== Proposal ==
=== Elements ===
* Envelope Element:
This element is used to 'bundle' together the parts of the message that need to be protected.
<envelope xmlns='...' encns='urn:xmpp:openpgp:0'>
  <crypt-specifix>
 
</envelope>
* CryptoSpecific Elements:
  * timestamp, padding etc.
== Whitelisting / Blacklisting ==
Its up to the implementation what to put into the envelope.
An implementation should put all the stuff that the server usually ignores in the envelope.
Whitelist for decryption
Use Registry for this
Things to think about:
Delay Tags vs. timestamps
121

edits

Navigation menu