https://bugs.kde.org/show_bug.cgi?id=523333
Tobias Fella <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM Status|REPORTED |RESOLVED --- Comment #2 from Tobias Fella <[email protected]> --- > Since we can't force all public bridges to change their configuration (and > they probably even can't, because self-signing would need more processing > power on the public bridge) and since the other clients do work and decrypt > the messages, NeoChat should try to decrypt the messages as well. Maybe it > can show the above warning when decrypting the first message or something to > let the user know, the message is not 100 % safe / private, but that is the > sacrifice of using public WhatsApp bridge, you need to trust the admin of the > bridge, as they can access the unencrypted messages. FWIW that's not the problem here, there's ultimately just a bug somewhere. Since this entire part of the code is going away in the next release of libquotient, there's no point in debugging it further. -- You are receiving this mail because: You are watching all bug changes.
