Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Fix #10: ensure device list and bundle are published after startup

Closes #10

See merge request !11

The condition wasn't necessary in session_start for PEP nodes not to be
published multiple times.

This also fixes the fact that we weren't publishing on reconnect.

And also fixes one indentation level too many in the _initial_publish
method.

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Automatically send heartbeats

See merge request !10

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

This would likely do that we had a fixed set of prekeys because we
wouldn't republish after one was used.

This shouldn't have any security implications. Just so that we wouldn't
have been able to initiate new sessions after all published prekeys were
used up, as we don't have the private keys anymore. They are deleted
when used (as should be) by the backend OMEMO library.

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

With this commit, slixmpp-omemo now reads the ratchet chain length,
(both receiving and sending), that we should track to know when to send
a heartbeat message.

This allows us to signal other devices that we are still active and
listening. Some clients will stop encrypting to us if we haven't replied
for a certain number of messages.

The current 0384 spec (0.7) says we should send a heartbeat message at
least once this number goes over 53 (fair dice roll). It doesn't say
when a client may/should stop encrypting to us, or what it should do at
all once we go over 53.

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Thanks mathieui

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

fp_from_ik: change fp repr to lowercase with no colon

See merge request !8

This allows the user to be able to do what they want with the string.
They can then insert colons, or split up in groups of chars or..

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Reuse changes from python-omemo, explicitly the following PR under CC0:
https://github.com/Syndace/python-omemo/pull/28



Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

preventing `variable not defined` exception when no option available

See merge request !5

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>