‘로그 익명화 세부 정보’ 설정이 사용자 이름을 완전히 익명화하지 않음

zogstrip · 1월 1, 2026, 12:52오후

사용자 이름 기준으로 항목을 삭제하는 것은 다소 까다롭고 위험할 수 있어, 대신 전체 context와 details 필드를 [removed due to user anonymization] 메시지로 대체하는 방식을 선택했습니다.

github.com/discourse/discourse

FIX: Clean up historical staff logs when anonymizing users (#36936)

main ← fix-anonymizer-historical-logs

merged 01:53PM - 14 Jan 26 UTC

ZogStriP

+47 -0

When `log_anonymizer_details` is disabled, the anonymization process correctly a…voids recording the old username in the new "anonymize_user" log entry. However, historical staff action logs created before anonymization (like "check_email") could still contain the original username in fields like `context` or `previous_value`, making it possible to link an anonymized user back to their original identity. For example, when an admin views a user's email from `/admin/users/123/johndoe`, the staff action log stores that URL path in the `context` field. After anonymization, this path still contains "johndoe", defeating the purpose of the setting. This fix passes the original username to the AnonymizeUser background job, which now scrubs any historical UserHistory records that contain the username. Rather than attempting error-prone string replacement, affected fields are replaced with "[removed due to user anonymization]" to make it clear why the data is missing while preserving the audit trail. Ref - https://meta.discourse.org/t/387500

글		댓글	조회수
User anonymization and staff_action_logs Support	6	771	8월 9, 2021
User still able to log in after anonymization Bug anonymization	3	174	11월 26, 2025
Username change logging even if it failed Bug	2	650	5월 13, 2019
Profile links not updated after anonymizing an user? Support anonymization	0	142	7월 5, 2021
Admins changing user's name (not username) should be logged Bug	4	805	11월 22, 2018

‘로그 익명화 세부 정보’ 설정이 사용자 이름을 완전히 익명화하지 않음

Related topics