-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for end-to-end encryption / olm library integration? #30
Comments
I chatted with some people about maybe getting an up-to-date olm gem built for the crypto purposes, but that seems to not really have gone anywhere. I've since started looking at maybe hacking together Ruby bindings for matrix-sdk-crypto, since that seems to be a modern and reasonable point to hook into for E2EE. They have FFI bindings as well, so a prototype using the ffi gem could definitely be done. |
Ah, that seems like a better/more-maintained solution. I haven't done any Ruby/Rust FFI before but I can certainly pitch in with testing and/or light Ruby stuff. I assume there's some useful prior art to help implement the protocol in the current Python libraries. |
I had started working on FFI bindings to |
Thanks for the project, it seemed quite useful until I hit this, and all of our rooms are E2E encrypted. Are there any possible workarounds at the moment? |
Unfortunately none that I can think of, I haven't personally had the time to dig deeper into matrix-sdk-crypto bindings - neither the magnus ones I started nor ffi. |
You could use pantalaimon to handle the E2EE part |
Hi! Thanks for this project, it's very useful.
Do you have any interest in using this Ruby olm library in order to implement e2e encryption? As it currently stands, I'm able to use this library pretty well, although the client shows up as unencrypted within encrypted rooms. The olm library is pretty old but seems to be explicitly focused on supporting Matrix's use of the algorithm.
The text was updated successfully, but these errors were encountered: