| Summary: | Previous encrypted messages are not decrypted if they were written in other client before verifying NeoChat | ||
|---|---|---|---|
| Product: | [Applications] NeoChat | Reporter: | Igor Mironchik <igor.mironchik> |
| Component: | General | Assignee: | Tobias Fella <fella> |
| Status: | RESOLVED FIXED | ||
| 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: | Room settings in Element | ||
|
Description
Igor Mironchik
2024-10-04 09:06:21 UTC
Did you activate the "Never send encrypted messages to unverified sessions from this session" checkbox in element? if you do that, it won't send encryption keys to unverified sessions Created attachment 174398 [details]
Room settings in Element
(In reply to Tobias Fella from comment #1) > Did you activate the "Never send encrypted messages to unverified sessions > from this session" checkbox in element? if you do that, it won't send > encryption keys to unverified sessions No, this option is turned off, look screenshot. NeoChat doesn't care whether it is verified or not. If messages can't be decrypted because neochat is unverified, that must be due to the sending device. That being said, my inital question was, of course, misguided: What matters is whether the sender's client is configured to only send encryption keys to verified devices, not yours. Your problem seems to be about messages that were sent before neochat was even logged in; decrypting those will be possible with the next release of libquotient, which is coming very soon. |