Skip to content

Conversation

Lokke
Copy link
Contributor

@Lokke Lokke commented Sep 30, 2025

removed possible personal data

removed possible personal data

Signed-off-by: Lokke <[email protected]>
@Lokke Lokke requested review from a team as code owners September 30, 2025 09:02
@ninjacatcher
Copy link
Contributor

What is your reason for wanting to delete this token? Where is this personal information? It's not an API token or anything else.

This UUID can be generated by a phisher to identify the victim, or this UUID means nothing at all, or is used as a key to access the phishing page.

@spirillen
Copy link
Contributor

What is your reason for wanting to delete this token? Where is this personal information? It's not an API token or anything else.

This UUID can be generated by a phisher to identify the victim, or this UUID means nothing at all, or is used as a key to access the phishing page.

It is a privacy concern, and the and the UUID can e used to track down the receiver, and thereby the reporters full identity, the UUID SHOULD be delete, including from the git history as well.

Copy link
Contributor

@spirillen spirillen left a comment

Choose a reason for hiding this comment

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

I approve this, but as it shall be removed from the git history as well, somebody else have to finish the jub

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.

3 participants