search

poljar / weechat-matrix

Weechat Matrix protocol script written in python
Other
954 stars 119 forks source link

Session verification on WeeChat client side seems not working #334

Open artshade opened 1 year ago

artshade commented 1 year ago

Dear Developer and Community,

Thank you very much for the awesome project!

I am sorry, but it appears there is a little documentation available on the subject of a Matrix session verification on the WeeChat side. For example, once the "Verify" button is pressed in the browser (e.g. Element) client, nothing appears in WeeChat and such command variations like /olm verify or /olm verification do result in success but errors like:

matrix: No matching unverified devices found. matrix: Device ABCDEABCDE of user user_example:matrix.org not found

The client though receives a cancelled event if, for example, the modal verification dialog (e.g. https://i.imgur.com/z47yBci.png ) in the browser client is closed and outputs:

matrix: The interactive device verification with user @user_example:matrix.org got canceled: User declined.

Is that expected and what are the exact steps to complete the verification of the session initiated via the plugin?

Best and kind regards

Related: https://alangrow.com/blog/weechat-matrix (Matrix Chat in the Terminal with weechat-matrix...)

poljar commented 1 year ago

Sadly the protocol has diverged from the initial implementation of the interactive verification and I was not able to keep up.

There's some support in the Rust version of weechat-matrix, but it also isn't done yet: https://github.com/poljar/weechat-matrix-rs/pull/56.

HeIIow2 commented 1 year ago

Hey I wanna use it as well but for the exact same reason I cant. That's unfortunate. I belive that security keys exist though which let you verify a device.

Is there a way to verify with those?

Best regards :)

3v1n0 commented 1 year ago

I was able to do it from the other side, so basically calling /olm verification start @your-user:matrix.org VERIFIED_DEVICE_ID, using a browser as other device worked.

leinher commented 1 year ago

I also struggled to get the verification process up and running.

@3v1n0 solution worked for me too. As I could not find a better place to document that I added a short step by step guide to the README.

See #352