Re: [Standards] JET-OMEMO Encrypted Jingle Transports

Good evening! I used your recent feedback to work on JET-OMEMO. The rendered result can be found here: http://geekplace.eu/xeps/xep-jet-omemo/xep-jet-omemo.html By limiting usable ciphers for JET-OMEMO to only aes-128-gcm-nopadding, I was able to reuse OMEMOs KeyTransportElement in the way it

Re: [Standards] JET-OMEMO Encrypted Jingle Transports

Am 7. Oktober 2017 10:52:25 MESZ schrieb Jonas Wielicki : >I would go with the simplest solution. IANAC (I Am Not A >Cryptographer), but >AES-128-GCM-NoPadding sounds fine to me. There’s no need to add >complexity >where none is needed. So limiting ciphers to

Re: [Standards] JET-OMEMO Encrypted Jingle Transports

Hi Paul and all, On Freitag, 6. Oktober 2017 10:12:02 CEST Paul Schaub wrote: > I'm currently working on JET-OMEMO, which will hopefully specify how to > use OMEMO with JET to encrypt Jingle Transports. > > One thing I'm not sure about is, whats the best way to encrypt the > Transport Key.

[Standards] JET-OMEMO Encrypted Jingle Transports

Hello everyone! I'm currently working on JET-OMEMO, which will hopefully specify how to use OMEMO with JET to encrypt Jingle Transports. One thing I'm not sure about is, whats the best way to encrypt the Transport Key. Initially I planned to treat the key as a message body. The resulting