Skip to content
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

Uable to verify #165

Open
aw-bib opened this issue Oct 6, 2023 · 2 comments
Open

Uable to verify #165

aw-bib opened this issue Oct 6, 2023 · 2 comments
Labels

Comments

@aw-bib
Copy link

aw-bib commented Oct 6, 2023

It seems that I lost the ability to verify my session in iamb.

If I send a verification request vai

:verify request @...:somewhere.org

another client sees the request. I can accept it and end up in Compare unique emoji. If I start the verification I would expect that :verify give me something to answer. But the list remains empty.

Element (aka "the other end") tells me:

Unverified session

This session doesn't support encryption and thus can't be verified.

On the iamb side I don't see anything that gives me a clue.

Note: I did have a verified session established in a former version of iamb (I think 0.0.7) and it worked nicely. This one also carried over to the new version. But it seems not possible to verify a new session in 0.0.8.

iamb 0.0.8

@ulyssa ulyssa added the e2ee label Oct 19, 2023
@tidux
Copy link

tidux commented Dec 14, 2023

Maybe it's an issue with your build environment? I was able to verify a new room with the Github release binary for 0.0.8 on Linux.

@aw-bib
Copy link
Author

aw-bib commented Apr 3, 2024

Maybe it's an issue with your build environment?

Unsure about that. I don't know the infrastructure too well here. (IOW for me all this rustup and cargo is still a bit of an adventure and of course I also ran into #237 ;)

Anyway, I may report though that with

iamb 0.0.9

that I just built yesterday the issue seems to be fixed and I was able to verify my iamb session from Element via emojis again.

I got a bit confused as 0.0.9 actually initiated a new session instead of reusing the former. And it even initiated yet another one, once I fiddled out the config changed to toml (#229) and I added a suitable toml file by converting my json one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants