One OMEMO key per device (browser) is really needed for secure e2ee though. Matrix has weakened their MegaOLM quite a bit by allowing devices to share one key per account. At some point you have to ask why e2ee at all when you water it down so much. Its not like normal TLS connections are unencrypted.
I’m very interested in the problem you describe. i also had UX issues dealing with keys in xmpp clients. if you’d like to talk about it some time and write some (more complete) feedback i’d be happy to help :)
One OMEMO key per device (browser) is really needed for secure e2ee though. Matrix has weakened their MegaOLM quite a bit by allowing devices to share one key per account. At some point you have to ask why e2ee at all when you water it down so much. Its not like normal TLS connections are unencrypted.
@poVoq have you ever tried to identify all your keys… and delete unneeded keys?
i tried a lot of clients. and now i have 50 keys or more, but need only 4 or 5 of them… not possibility to delete the others.
Conversations autodeletes after 42 days, but this makes for frustration at the other end: “conversations deletes dormant keys too soon” [paraphrasing] https://github.com/iNPUTmice/Conversations/issues/4147
If it is really only 4-5 why not just delete them all and make new ones?
@poVoq
I told you… try it… i does not work. not in gajim, not in movim, not in conversations…
i tried it.
@poVoq they will come back or are not able to be deleted…
I’m very interested in the problem you describe. i also had UX issues dealing with keys in xmpp clients. if you’d like to talk about it some time and write some (more complete) feedback i’d be happy to help :)