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

Prevent plugin_e2ee from sending empty JID as recipient

See merge request poezio/poezio!56

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

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

BasePlugin: Remove debug logging

See merge request poezio/poezio!55

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

E2ee muc

See merge request poezio/poezio!53

This change transmits the original JID of the sender (in decrypt) or
receiver(s) (in encrypt).

Handling of MUC is not complete. It is possible that some participants
have access to realjids while others don't (e.g., moderators in
semi-anon MUCs).

The code currently doesn't handle this and this will cause at least two
issues:
- Sending an encrypted message in a semi-anon MUC would reveal the
  sender's identity (public key)
- Recipients wouldn't be able to decrypt this message as they don't have
  access to the sender's realjid. Unless they already have the bundle
  available and then they could associate the public key with a jid
  (another privacy issue/defeating the point of semi-anon rooms).

TODO: Fix this ^

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>

E2EE plugins support

See merge request poezio/poezio!18

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>

decrypt_message now takes an Encrypted container and a sender (JID)
instead of a Message object.

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

slixmpp-omemo's get_trust_for_jid doesn't provide fingerprints directly
anymore, it simply wraps the omemo lib method.

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

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

We're not supposed to see MissingBundleException directly as it's
handled by slixmpp-omemo. Slixmpp-omemo will give us all the remaining
exceptions via EncryptionPrepareException when it doesn't know what to
do anymore.

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>

mathieui authored Aug 25, 2019 and Maxime Buquet committed Dec 27, 2019

- supported tab types is a list of tabs this plugin should be active in
 (only chattabs)
- trust_states is a dict[str → set] containing only two keys: accepted
 and rejected, whose values are the internal plugin states that should
 allow encryption and the ones that should not

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

mathieui authored Aug 23, 2019 and Maxime Buquet committed Dec 27, 2019

(yes, another one)

mathieui authored Aug 23, 2019 and Maxime Buquet committed Dec 27, 2019

(do not try to rely on the current tab)

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

mathieui authored Aug 23, 2019 and Maxime Buquet committed Dec 27, 2019

So errors don’t get caught