E2EE instability

[Half-Shot]

We've just added E2EE support to hookshot, which is fantastic. However, it's also a bit unstable and we need to iron out some bugs. I'm leaving this issue open to track anything that might pop up while it's new.

If you are an administrator of a hookshot deployment and have tried to use the encryption feature:

• Please note, that it's very unstable and should only be used in a testing environment.
• Please report any bugs you find in this issue, so we can keep track and deal with them.

[jaller94]

Filed Failed to set up crypto on intent (IO error: could not acquire lock)

[Half-Shot]

#714 should help us massively with this.

[Half-Shot]

And fixed!

[thoraj]

Does this mean that the comment in Hookshot about E2EE instability could be removed? (https://matrix-org.github.io/matrix-hookshot/latest/advanced/encryption.html)

Or is there more work remaining to get E2EE in Hookshot production ready?

[ownerer]

Bump, wondering the same as @thoraj ?
Mind chiming in here real quick @Half-Shot :) ?

[tswfi]

Kinda interested also :)

[olmari]

@Half-Shot So, which one is it, fully supported or still highly experimental like https://matrix-org.github.io/matrix-hookshot/latest/advanced/encryption.html still says? How about the current state of needed expoerimentals on synapse side?

[ownerer]

I created a new follow-up issue in an attempt to get more visibility (seeing as this issue is closed) and get some clarity on these questions.
See #845