-
Notifications
You must be signed in to change notification settings - Fork 70
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
[v0.6.0-beta.8] "One time key signed_curve25519:AAAABw already exists." #237
Comments
The access token was already used to set up encryption for that device: a fresh access token may be required. Edit: Element sets up encryption, so using a script like the |
Thanks, that works! Is it possible to verify the bot's device? And, is it possible to import E2E room keys into the bot? |
verification isn't supported, but manual verification of the bot is always a thing you can do. Importing room keys is also not supported at the moment. |
Sorry to bother you but could you please give me a pointer for how one would accomplish this? Or, would it perhaps make more sense to use Edit: never mind, I reimplemented my bot with |
Hello, I've been looking for several days how to do this manually, but I can't find the right eventName to listen to "m.key.verification.request" nor any to_device event, what am I missing? Thanks for you job !! big stuff Edit: Thank to @turt2live to give me |
Hi, thanks for this project!
I'm trying to use it to write a bot which acts on my behalf to automate some things. As such, it runs under my account.
I noticed that the last stable version (
v0.5.9
) could not decrypt encrypted messages, so I'm tryingv0.6.0-beta.8
.Upon adding a
RustSdkCryptoStorageProvider
instance and passing it toMatrixClient
, it crashes printing this:Perhaps this is because I'm trying to run it on an existing user? To do this, I opened an Element instance in a private window, logged in as myself, got the token, approved the instance from another client (by comparing emoji), then closed the private window.
Also, I don't know if this is relevant or not, but I noticed that in the
signatures
object in the message above, I see instances with the same key ('ed25519:DYFH******'
) but different values ("r5Am..."
and'2z2W...'
).Hope this helps!
The text was updated successfully, but these errors were encountered: