On Sat, Apr 6, 2019 at 5:59 PM, Jonas Schäfer
wrote:
I agree with Florian fully. This is rather non-idiomatic to implement
on the
client side, due to how XMPP works otherwise. The flow suggested by
Florian is
more idiomatic and implementable with less brain-hurt.
I don’t see any advantage
On Donnerstag, 4. April 2019 12:52:15 CEST Florian Schmaus wrote:
> On 02.04.19 10:07, Evgeny wrote:
> > On Mon, Apr 1, 2019 at 9:40 PM, Florian Schmaus wrote:
> >> I am a little bit worried that this will take a few detours to implement
> >> cleanly and elegant in clients and client libraries.
On 02.04.19 10:07, Evgeny wrote:
> On Mon, Apr 1, 2019 at 9:40 PM, Florian Schmaus wrote:
>> I am a little bit worried that this will take a few detours to implement
>> cleanly and elegant in clients and client libraries. Especially since
>> this pattern never occurred before.
>>
>> Instead I
On Mon, Apr 1, 2019 at 9:40 PM, Florian Schmaus
wrote:
I am a little bit worried that this will take a few detours to
implement
cleanly and elegant in clients and client libraries. Especially since
this pattern never occurred before.
Instead I suggest the following control flow, which should
On 30.03.19 16:48, Jonas Schäfer (XSF Editor) wrote:
> Version 0.1.0 of XEP-0417 (E2E Authentication in XMPP: Certificate
> Issuance and Revocation) has been released.
>
> Abstract:
> This specification defines a way for a certificate authority to serve
> certificate signing requests via XMPP in
Version 0.1.0 of XEP-0417 (E2E Authentication in XMPP: Certificate
Issuance and Revocation) has been released.
Abstract:
This specification defines a way for a certificate authority to serve
certificate signing requests via XMPP in order to issue X.509
certificates for the use in end-to-end and
