[Standards] OMEMO Key Agreement v2

Chris Ballinger chrisballinger at gmail.com
Wed May 31 20:39:01 UTC 2017


My ideal scenario is one where the existing OMEMO implementations do not
need to change anything, including republishing their identity keys in a
new format. I think that non-libsignal clients should be responsible for
the conversions on their end.

On Wed, May 31, 2017 at 11:36 AM, Remko Tronçon <remko at el-tramo.be> wrote:

> Hi,
>
> Here's a proposal for the OMEMO key exchange that requires *no* changes to
> libsignal: Public Identity keys are Ed25519 keys with the highest bit (sign
> bit) 0.
>
> - LibSignal-based clients convert their internal Curve25519 identity key
> to Ed25519 right before the device bundle publish IQ, and convert the peer
> key to Curve25519 when fetching the bundle IQ.
> - On device initialization, non-libsignal clients guarantee a keypair that
> LibSignal can handle by generating identity keypairs until the highest bit
> of the public key is set to 0 (there's a 1 in 2 chance).
>
> Chris Ballinger seemed open to this proposal.
>
> Remko
>
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
> _______________________________________________
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20170531/54966bbb/attachment.html>


More information about the Standards mailing list