You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When posts are made, the poster_name is put on the message, and is populated with the member_name field, which is intended to be the private name, not the public display name (real_name).
Normally not an issue, because it's not displayed anywhere under normal circumstances.
BUT... If that user is deleted, the poster_name is now displayed on the message... Also if that deleted user is quoted, the poster_name/member_name is displayed in the quote... If the board is public, that info becomes public.
This may be considered a privacy concern. The main reason folks request deletion is for privacy reasons - and the way it works now, upon deletion, the member_name ends up getting exposed.
I thought this was reported earlier, can't seem to find it...
Steps to reproduce
Have a user with separate member name & display name
Delete the user, but keep the posts
Expected result
Should never see the private member_name exposed.
Actual result
The private member_name is exposed.
Version/Git revision
2.1.4
Database Engine
All
Database Version
No response
PHP Version
No response
Logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Basic Information
When posts are made, the poster_name is put on the message, and is populated with the member_name field, which is intended to be the private name, not the public display name (real_name).
Normally not an issue, because it's not displayed anywhere under normal circumstances.
BUT... If that user is deleted, the poster_name is now displayed on the message... Also if that deleted user is quoted, the poster_name/member_name is displayed in the quote... If the board is public, that info becomes public.
This may be considered a privacy concern. The main reason folks request deletion is for privacy reasons - and the way it works now, upon deletion, the member_name ends up getting exposed.
I thought this was reported earlier, can't seem to find it...
Steps to reproduce
Expected result
Should never see the private member_name exposed.
Actual result
The private member_name is exposed.
Version/Git revision
2.1.4
Database Engine
All
Database Version
No response
PHP Version
No response
Logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: