Project

General

Profile

Actions

Bug #85316

closed

Anonymize IP scheduler tasks does not clean up log_data field

Added by Felix Nagel over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
scheduler
Target version:
-
Start date:
2018-06-20
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
On Location Sprint

Description

When using the new scheduler task (TYPO3\CMS\Scheduler\Task\IpAnonymizationTask) for anonymizing IP addresses (by default in sys_log table) some occurrences of a IP might be still existing.

Example (for logging a BE user login):

# Before task
details: User %s logged in from %s (%s)
IP: 123.456.789.123
log_data: a:3:{i:0;s:8:"john.doe";i:1;s:15:"123.456.789.123";i:2;s:0:"";}

# After task
details: User %s logged in from %s (%s)
IP: 123.456.789.0
log_data: a:3:{i:0;s:8:"john.doe";i:1;s:15:"123.456.789.123";i:2;s:0:"";}

The data used for the log module (field log_data)still contains the full IP address.
Not quite sure if there are more log item types that save the IP within the serialized data.


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Feature #84053: Anonymize IPsClosedGeorg Ringer2018-02-27

Actions
Related to TYPO3 Core - Epic #84776: Initiative GDPRClosedGeorg Ringer2018-02-272018-05-28

Actions
Precedes TYPO3 Core - Bug #85773: Flaws in sys_log entry IP anonymizationClosedMarkus Klein2018-06-212018-06-21

Actions
Actions

Also available in: Atom PDF