Skip to content

Conversation

iequidoo
Copy link
Collaborator

@iequidoo iequidoo commented Aug 5, 2025

Probably needs a test.

…ed 1:1 message

For encrypted 1:1 messages we don't check the recipient fingerprint currently, so check that we
don't have multiple key-contacts with the given recipient address.
@@ -3869,7 +3885,7 @@ async fn lookup_key_contact_by_fingerprint(
.sql
.query_row_optional(
"SELECT id FROM contacts
WHERE fingerprint=? AND fingerprint!=''",
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's already a check above

@iequidoo
Copy link
Collaborator Author

iequidoo commented Aug 14, 2025

I have no idea how to improve this. If we have multiple key-contacts with the given address, we need to assign the message to one of them and we now prefer to choose accepted contacts. But anyway we may select a blocked contact, in this case assigning the message, but not unblocking the chat, looks like a lesser harm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant