GitLab

Denis Kasak authored May 20, 2021 and Hubert Chathi committed Jun 04, 2021

The old docstring was the same as olm_create_inbound_session and didn't
explain the difference between them.

olm::decode_base64 now returns the length of the raw decoded data on
success. When given input with an invalid base64 length, it fails early
(before decoding any input) and returns -1.

This also makes the C function _olm_decode_base64 an actual binding of
olm::decode_base64 instead of a wrapper with slightly different
behaviour.

Lukas Lihotzki authored Apr 26, 2021 and Hubert Chathi committed Apr 27, 2021

Signed-off-by: Lukas Lihotzki <lukas@lihotzki.de>

Saúl Ibarra Corretgé authored Sep 23, 2020 and Hubert Chathi committed Sep 23, 2020

Also make olm_sas_generate_bytes fail if their key wasn't set.

instead of having a static one, as that could end up taking up a
lot of memory if your app keeps olm sessions hanging about.

As a way to dump the state of an olm session, ie. the chain indicies,
so we can debug why olm sessions break and get out of sync.

The python that searches the header files for exports isn't smart
enough to know what is a comment and what isn't, so it picks this
up too and emscripten then complains about it being undefined.

also make some params const where possible

(cherry picked from commit c0a53ebaeda420f636698b99c393868d2bf8f905)

Change interface to allow the app to get the private part of the
key and instantiate a decryption object from just the private part
of the key.

Changes the function generating a key from random bytes to be
initialising a key with a private key (because it's exactly the
same thing). Exports & imports private key parts as ArrayBuffer at
JS level rather than base64 assuming we are moving that way in
general.

This disrupts building at least with Visual Studio.
Signed-off-by: Alexey Rusakov <ktirf@users.sf.net>

olm_import_inbound_group_session, which reads the format written by
olm_export_inbound_group_session to initialise a group session.

A pair of functions which allow you to export the megolm keys for an inbound
group session, so that an application can save/restore them.

All the other methods clear their random inputs. This one needs to do the same,
to reduce the risk of the randomness being used elsewhere and leaking key info.

Applications can use the index to detect replays of the same message.