View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0011254GNUnetmessenger servicepublic2026-03-15 21:162026-03-15 21:16
Reporterthejackimonster Assigned Tothejackimonster  
PrioritylowSeverityminorReproducibilitysometimes
Status assignedResolutionopen 
Product VersionGit master 
Target Version1.0.0 
Summary0011254: Read receipts do not ensure individual decryption
DescriptionWhen user's send a message to other members of a chat room, they typically receive a read receipt which corresponds to any message sent by the other member following the original sent message from the user. However this does not account for encrypted messages (PRIVATE or SECRET messages).

In this case a user might assume their message has been received while only the encrypted message has been received, potentially without the recipient being able to decrypt and read it yet. So in this case the service/chat-library/application should ensure that the encrypted message and the associated key have been transmitted before confirming via a visual "read receipt".
Steps To Reproduce- Send an encrypted message (any TEXT message in a private chat works).
- Cut connection after sending the encrypted message but before sending the message providing its key (so in case of the epoch encryption to ensure forward secrecy that would be the ACCESS message).
- Check whether you have a read receipt for the TEXT message.
Additional InformationThe issue is mostly on application level, caused by libgnunetchat but it might be necessary to make changes to the Messenger service fixing it.
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2026-03-15 21:16 thejackimonster New Issue
2026-03-15 21:16 thejackimonster Status new => assigned
2026-03-15 21:16 thejackimonster Assigned To => thejackimonster