Bug 494111

Summary: Message encrypted by device not verified by its owner may be shown encrypted
Product: [Applications] NeoChat Reporter: Igor Mironchik <igor.mironchik>
Component: GeneralAssignee: Tobias Fella <fella>
Status: RESOLVED UPSTREAM    
Severity: normal CC: carl
Priority: NOR    
Version First Reported In: 24.08.1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: How it looks in Element

Description Igor Mironchik 2024-10-04 13:38:48 UTC 
Created attachment 174411 [details]
How it looks in Element

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
In Element I have a room, and opponent reported there with "Encrypted by device not verified by its owner". In this case NeoChat shows message from him with "This message is encrypted and the sender has not shared the key with this device.", but restarting of NeoChat may show some of them, some of them keep encrypted.


STEPS TO REPRODUCE
1. Make a room with person with "Encrypted by device not verified by its owner". I don't know how to do it on other side... Ask Carl Schwan how he did it.
2. Chat with opponent.
3. 

OBSERVED RESULT
Messages from him may be shown as  "This message is encrypted and the sender has not shared the key with this device." In Element messages are shown, but marked - look at the attached screenshot.

EXPECTED RESULT
I'd like to see a message.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: KDE neon 6.0
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Comment 1 Tobias Fella 2024-12-12 20:34:39 UTC 
Hi!

We're currently completely reworking the support for end-to-end-encryption and related features in libquotient, the library NeoChat uses internally. While this certainly won't magically fix all bugs we're currently seeing in NeoChat related to these features, it is unlikely that the exact same problems are still affecting NeoChat after the new version of libQuotient. You can track this work at https://github.com/quotient-im/libQuotient/pull/820

The ongoing work on the new cryptography backend also means that we won't be able to spend any time on investigating problems with the current implementation, such as this problem. I will thus close this issue, as it won't be applicable after the switch anymore.  Thanks for your understanding :)