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

OMEMO qrcode could not be scanned/ no reaction after scan #4432

Open
fleixi opened this issue Dec 27, 2022 · 4 comments
Open

OMEMO qrcode could not be scanned/ no reaction after scan #4432

fleixi opened this issue Dec 27, 2022 · 4 comments

Comments

@fleixi
Copy link

fleixi commented Dec 27, 2022

If i try to scan the qrcode from an other users account setting the new key doesn't get added to my account and it is not possible to chat with encryption. There is no visual feedback after scanning the code. the scanning just stops. There is no new key added to the contact.

This is tested on multiple devices with 3 accounts.

Version is 2.11.2+free from f-droid.

@licaon-kter
Copy link

licaon-kter commented Dec 27, 2022

What does a QR scanner show when you scan that code?

Note that the key is not added to "your account" but to that "contact"

Did you read #4410 too?

@iNPUTmice
Copy link
Owner

Scanning the QR code does not add keys. It verifies keys. If you ignore the QR code scanning for a second

it is not possible to chat with encryption

This is your problem. This should work regardless. No scanning necessary.

Is there an error message somewhere? Do all servers in question support OMEMO? What if you let the other side start initiate an encrypted chat first?

@fleixi
Copy link
Author

fleixi commented Dec 30, 2022

if i scan the code with an other tool i get this:

xmpp:[email protected]?omemo-sid-484457286={longhash}

i have read #4410 but this is an other error. the qrcode is correct but it will not be added anywhere after scanning. there is no errormassage on any gui.

I could recreate this error on 3 different devices. Manuel adding a new OMEMO-key via qrcode is not possible and i as a second problem, i could not delete the old keys too.

If i try to use the blindtrust function by new contacts there is no new key selectable too. Only the old, not valid, key is displayed to enable.

I run into this problem first after doing an factory reset on one device with is using OMEMO with the exact same server, account and device before without any problems. So the server is supporting OMEMO.

It doesn't matter with side is starting the chat first. The problem is that both clients using an unknown key for the other side to encrypt.

The problem could recreated with a chat between conversation and pidgin too.

I think the problem is that the new key is not be added to the devicestore. Sidenote: All devices have get a update to Android 12 recently. Maybe something has changed for saving the key.

@licaon-kter
Copy link

licaon-kter commented Dec 30, 2022

Can you make 2 accounts on conversations.im server and test between them?

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

No branches or pull requests

3 participants