On 19.09.2017 12:35, Remko Tronçon wrote:
>
> The original authors of the XEP worked on a follow up version [1] which
> put the wire format into the XEP
>
>
> This follow-up version is in its current state even more underspecified
> than the libsignal one (for example, it's impossible to
> The original authors of the XEP worked on a follow up version [1] which
> put the wire format into the XEP
This follow-up version is in its current state even more underspecified
than the libsignal one (for example, it's impossible to know how to
authenticate the sent payload IIRC).
> and was
On 19.09.2017 11:37, Dave Cridland wrote:
> On 19 September 2017 at 09:21, Klaus Herberth wrote:
>>> Hi Klaus,
>> Hi Andrey,
>>
>>> What do you mean by "libsignal"? There are at least 4(+1) libraries:
>> With libsignal I referred to your linked implementations of WhisperSystems.
>>
>>> Note, javas
On 19 September 2017 at 09:21, Klaus Herberth wrote:
>> Hi Klaus,
> Hi Andrey,
>
>
>> What do you mean by "libsignal"? There are at least 4(+1) libraries:
> With libsignal I referred to your linked implementations of WhisperSystems.
>
>> Note, javascript favor is already available.
> I know, but i
> Hi Klaus,
Hi Andrey,
> What do you mean by "libsignal"? There are at least 4(+1) libraries:
With libsignal I referred to your linked implementations of WhisperSystems.
> Note, javascript favor is already available.
I know, but it is GPL and this doesn't work for everyone.
> BTW, why is it
Hi Klaus,
On 2017-09-18 15:27, Klaus Herberth wrote:
Hi Paul,
thanks for reading that lengthy email.
If I understand you correctly, the complete magic happens in the key
element and there is no description in the XEP or in the linked
"signal protocol" which describes it. So all implementations
I summarized open questions that need to be discussed for 'OMEMO-NEXT'
in this mail:
https://mail.jabber.org/pipermail/standards/2017-June/033018.html
2017-09-18 16:57 GMT+02:00 Klaus Herberth :
> Hi Daniel,
>
> thanks for the clarification. Is there already something done for
> OMEMO-next? Whe
Hi Klaus,
thanks for the clarification. Is there already something done for
> OMEMO-next? Where can I contribute?
>
I have a long list of proposals I want to submit to the XEP (many of them
here https://github.com/xsf/xeps/pull/463, but some might need revisiting
in light of some discussions). Ho
Hi Daniel,
thanks for the clarification. Is there already something done for
OMEMO-next? Where can I contribute?
> Why we use an authentication tag?
No, this is clear, but the GCM spec [7] uses only the term additional
authenticated data, so I was wondering if this is the same.
Cheers
On 18.09
As I said, there is no such thing as a "signal protocol" (as far as I
know), there is only the libsignal implementation and a bunch of specs.
> It seems you dont have a SignalProtocol implementation, and are
> searching in this XEP for answers how to implement SignalProtocol.
That's right, but th
I suggest you go dig up the old conversations from the archive on why
we made the 'change' to the siacs namespace.
TLDR; the 'siacs' XEP describes the current situation and people are
planning on doing some larger changes to OMEMO that might take a very
long time to complete. Thus we wanted to hav
The section says that the key element contains the encrypted payload, which
was encrypted with a SignalSession.
I think its out of scope for the XEP to describe what a SignalSession
encrypted payload (a SignalMessage) contains.
The XEP is about using the SignalProtocol with XMPP, not about how
Sign
Hi!
Am 18.09.2017 um 15:27 schrieb Klaus Herberth:
>
> Hi Paul,
>
> thanks for reading that lengthy email.
>
> If I understand you correctly, the complete magic happens in the key
> element and there is no description in the XEP or in the linked
> "signal protocol" which describes it. So all impl
Hi Paul,
thanks for reading that lengthy email.
If I understand you correctly, the complete magic happens in the key
element and there is no description in the XEP or in the linked "signal
protocol" which describes it. So all implementations use libsignal? I
think this is terrible for a protocol
Hi!
Am 18.09.2017 um 13:07 schrieb Klaus Herberth:
>
> I am trying to create an MIT licensed OMEMO library written in
> Typescript and while reading the protocol some questions came up.
>
Nice! OMEMO lacks permissive implementations.
> - Version 0.2 uses the signal protocol now (sec 1.1), but as
Hi everyone,
I am trying to create an MIT licensed OMEMO library written in
Typescript and while reading the protocol some questions came up. I hope
someone can answer these or help me to improve the protocol (currently
0.2 [1]).
- Version 0.2 uses the signal protocol now (sec 1.1), but as far as
16 matches
Mail list logo
