Since the update to Gajim v1.0.0 I am no longer able to untrust fingerprints while it is still possible to trust them. Once the "Trust" is set to "True" it cannot be set back to "False".
Some behaviour when using the "Known Fingerprints" Tab in the plugin configuration and the fingerpring dialog when in a chat with another contact and enabled OMEMO.
Edited
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Activity
Sort or filter
Newest first
Oldest first
Show all activity
Show comments only
Show history only
spicewieselchanged title from omemo - untrusting fingerprints does not work with Gajim v1.0.0 and omemo 2.5.7 to [OMEMO] - untrusting fingerprints does not work with Gajim v1.0.0 and omemo 2.5.7
changed title from omemo - untrusting fingerprints does not work with Gajim v1.0.0 and omemo 2.5.7 to [OMEMO] - untrusting fingerprints does not work with Gajim v1.0.0 and omemo 2.5.7
Maybe it's just that the buttons on the popup dialog don't clearly state "trust"/"revoke" but just "yes"/"no"? That had me confused for a moment. Re-coloring works on my end, but only already trusted contacts, not on undecided ones.
Yes, I am on Gajim v1.0.1 and omemo-plugin v2.5.11 and still not able to de-trust a once trusted fingerprint.
I added a new contact right now and got one key for it. With this account I am able to de-trust this key, while it still does not work with the other ones...
Today I saw that this depends on the fingerprint. I can de-trust some fingerprints and some not, within the same contact and independent from the fingerprints' status like in-use or not-used (greyed out)
I am able to revoke (Conversation Tab, Click on the shield icon, select key, click on "Trust/Revoke Fingerprint -> choose No) just one of the active fingerprints. Doing this to the other 3 fingerprints does not have any effect. They stay "True".
I see the same behaviour if I try to revoke a fingerprint via plugin configuration -> Known Fingerprints.
If someone tells me to revoke his FP (maybe after the phone was stolen) all I could do right now is to delete this known fingerprint, then send another message to get it back from the server and to NOT trust it afterwards.
Checked with some colleagues, they've got the same issue.
sorry for the late reply, I was on holiday and forgot to process here afterwards.
I am now on gajim-omemo-plugin 2.6.1 and still got that issue. Just tested it with a contact I got 6 fingerprint for. 2 active (green), 4 inactive (grey). I can disable both green entries but just 2 of the 4 grey ones.
i just saw this also on my machine, deleting the fingerprint and redownloading helped
i looked at the db and a select query fails to find the entry, so nothing is changed, i did not find the reason why it fails, just that deleting the fingerprint and redownloading it helped
Its a sqlite bug in my opinion, not much we can do about it at this point, i check if we can store the fingerprint in another format in the db
1
Daniel Brötzmannchanged title from [OMEMO] - untrusting fingerprints does not work with Gajim v1.0.0 and omemo 2.5.7 to [OMEMO] - Untrusting fingerprints does not work (SQLite query error)
changed title from [OMEMO] - untrusting fingerprints does not work with Gajim v1.0.0 and omemo 2.5.7 to [OMEMO] - Untrusting fingerprints does not work (SQLite query error)