Support E2E encryption

[maralorn]

No description provided.

[ara4n]

The implementer's guide for E2E is now pretty much complete, and libolm and megolm is good to go. We'll hear initial feedback from the audit on Tuesday (Oct 4), but we're not expecting any showstoppers to emerge from it (hopefully!)

https://docs.google.com/document/d/17zpoQYFuE-vU5aiVpGxJi-KiMqvULP4RFMZnzyr3i6U/edit#

[ghost]

I started a BountySource bounty for this.

[ptman]

There has been some work in libqmatrixclient: quotient-im/libQuotient#95

[ghost]

I literally cannot use Quaternion until this is implemented, since all of my personal conversations are encrypted. This is a shame; it otherwise looks like an excellent client.

[a-andreyev]

E2EE is not there yet, it was my GSoC project. TLDR: receiving is kinda there, sending and other stuff are not ready yet.
You also could try a reverse proxy daemon called pantalaimon to use E2EE with any client if it's urgent for you.
Since it's a spare-time project, pull requests are more than welcome. Really hope we could make you happy soon :)

[lbeltrame]

Quaternion does not work with pantalaimon unfortunately, because it "detects" rooms as E2EE and refuses to send messages, even with pantalaimon proxying them. That happened a while ago, not sure about now.

[ddobrev]

Hello, is this going to be added any time soon?

[Midek]

Would it be possible to somehow disable this whole broken e2ee in quaterion so it does not interfere with pantalaimon?

[a-andreyev]

Would it be possible to somehow disable this whole broken e2ee in quaterion so it does not interfere with pantalaimon?

You could track the pantalaimon interoperability issue status in the #663

[KitsuneRal]

See #663 on fixing the situation with Pantalaimon. E2EE in Quaternion is still work in progress, and will be for a bit of time yet (it's moving now, albeit slowly).

[goodboy]

wen

[Akselmo]

Has there been any updates on this front?

[KitsuneRal]

There are a good news and a bad news here. Thanks to the NeoChat team, there's steady progress on the libQuotient front (see quotient-im/libQuotient#443). Don't want to promise any timelines at the moment but there's a plan to at least partially merge this work in the next stable version of libQuotient (0.7). The bad news is that this will only enable E2EE basics in Quaternion (sending/receiving messages and minimal device approval/cross-signing UI) which should come more or less in sync with libQuotient; anything advanced (emoji-based cross-signing, backup etc.) that would make E2EE actually usable is unlikely to arrive in the nearest half a year or even a year, judging by the experience Nheko fellas went through. That's really pending on the amount of effort put into this; extra qualified hands/minds can speed it up substantially.

[KitsuneRal]

For those craving for it - 0.0.96 beta has some basic support of E2EE (mainly along the lines described in the previous comment; also, see the libQuotient 0.7 release notes). Decrypting historical encrypted messages is down to the library support that will hopefully arrive in 0.7.2 or 0.7.3; cross-signing is not there but might be closer thanks to all the work done in NeoChat; and backups might wait until 0.0.97.

[KitsuneRal]

Another status update for those subscribed to this issue: there are more incremental updates in 0.0.96 beta 3 thanks to switching to libQuotient 0.8. Unlike the previous beta, you can switch E2EE per-account now, at runtime. Historical messages are still not decrypted; the library support for cross-signing is in the works and hopefully will land in libQuotient 0.8.x version.

[AdamWill]

So it looks like libquotient got cross-signing support in 0.9, but it also requires work on the client side. I don't see it mentioned in quaternion commits since the lib got bumped, so is this back on quaternion now?