GitLab

Summary

Two new accounts, both of them opened with poezio, conversations and dino. One manages to encrypt and be decrypted by everyone, but the account that replied fails one of these steps, only when sending via poezio.

Versions

• poezio: !248 (merged) (8b00e25a)
• poezio-omemo (17318815db29003a907b2c9def1855528513d8fb)
• slixmpp-omemo (f1750d6df32504fdaf6f478b71191f80aa69d7bf)
• python-omemo (f0c44fd)
• python-omemo-backend-signal (30b378d)
• python-doubleratchet (95524cf)
• python-x3dh (a38d9ec)
• python-xeddsa (5b6b93b)
• Dino (6f9375e6ea524ac5b1d36b05a99e9b90a0ac866d)
• Conversations (2.10.2+fcr)

Steps

• New AccountA, AccountB
• Open both accounts on Poezio{A,B}, Conversations{A,B}, Dino{A,B}. Conversations is the same instance, Dino as well. Only Poezio{A,B} are different instances (no multi-account).
• Poezio's 'omemo' plugin added in the configuration before clients are started, so the two accounts start with a public key and bundle (poezio has been started first, but it probably doesn't matter).
• Add each other as contacts.
• Send a plaintext message from PoezioA, everybody reads it.
• Send an encrypted message from PoezioA, everybody reads it.
• Send an encrypted message from DinoB, everybody reads it.
• Send an encrypted message from PoezioB, nobody reads it ("This message is encrypted [..]"), except PoezioA.
• Send another encrypted message from PoezioB, nobody reads it, except PoezioA.
• Send an encrypted message from PoezioA, everybody reads it.

What I expect

Everybody should be able to see PoezioB's messages.