diff options
| author | Alexey Rusakov <Kitsune-Ral@users.sf.net> | 2022-06-24 15:10:33 +0200 |
|---|---|---|
| committer | Alexey Rusakov <Kitsune-Ral@users.sf.net> | 2022-06-24 15:10:33 +0200 |
| commit | 6ae41d68dcdb91e5ec4a3ea48a151daaa0765765 (patch) | |
| tree | f715eba9e690e8faa7de729b82ee82d9e0b30962 /lib/csapi/definitions/auth_data.h | |
| parent | 9f7a65b04c246de4c27b205ece778ede1ad7df7e (diff) | |
| download | libquotient-6ae41d68dcdb91e5ec4a3ea48a151daaa0765765.tar.gz libquotient-6ae41d68dcdb91e5ec4a3ea48a151daaa0765765.zip | |
Rework SignedOneTimeKey as a QJsonObject wrapper
Since this object has to be verified against a signature it also carries
there's a rather specific procedure described in The Spec for that.
That procedure basically assumes handling the signed one-time key
object as a JSON object, not as a C++ object. And originally Quotient
E2EE code was exactly like that (obtaining the right QJsonObject from
the job result and handling it as specced) but then one enthusiastic
developer (me) decided it's better to use a proper C++ structure -
breaking the verification logic along the way. After a couple attempts
to fix it, here we are again: SignedOneTimeKey is a proper QJsonObject,
and even provides a method returning its JSON in the form prepared for
verification (according to the spec).
Diffstat (limited to 'lib/csapi/definitions/auth_data.h')
0 files changed, 0 insertions, 0 deletions