Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

data breach when editing messages in a group #6880

Closed
2 tasks done
RES-1 opened this issue May 20, 2024 · 2 comments
Closed
2 tasks done

data breach when editing messages in a group #6880

RES-1 opened this issue May 20, 2024 · 2 comments

Comments

@RES-1
Copy link

RES-1 commented May 20, 2024

Using a supported version?

  • I have searched searched open and closed issues for duplicates.
  • I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

When a message is edited in a group, group members who were not yet members of the group at the time the message was originally created also receive the message.

Steps to reproduce

  • create message in group;
  • add member;
  • edit original message;

Expected result

The edited message will not be displayed to the new group member.

Actual result

The edited message is displayed to the new group member.

Screenshots

No response

Signal version

7.9.0

Operating system

GNU/Linux/Fedora/KDE

Version of Signal on your phone

7.6.2

Link to debug log

No response

@ayumi-signal
Copy link
Contributor

Hi, thanks for the report. It's not our intention that people can see messages they weren't sent originally, so we'd like to find out what's going on.
We tried to reproduce but weren't able to. Could you please provide more info:

  • Debug logs (View Menu -> Debug Logs)
  • More details on repro steps -- Does the group invite result in Message request or have they been in contact before; is the group add being done from Desktop and not the mobile clients? and any other details you can remember.

@RES-1
Copy link
Author

RES-1 commented May 21, 2024

I have now created a test environment for this myself. It was a misjudgment that the new member would see the changed message. I apologize for the incorrect error message. The error arose because the changed message indicated in the informations that it was sent to the new member. However, this is just a “cosmetic flaw”.

@RES-1 RES-1 closed this as not planned Won't fix, can't repro, duplicate, stale May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants