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
If the privacy feature introduced in Matomo 3.5.0 is enabled and the userId is hashed with a salt, then the visitorId would still kind of leak the userId. Ideally, when the userId is set and the feature is enabled, then the userId should be salted there as well.
The text was updated successfully, but these errors were encountered:
tsteur
added
the
Bug
For errors / faults / flaws / inconsistencies etc.
label
May 8, 2018
Actually, it should not be an issue as manipulateRequest in privacy manager "request processor" is executed before getting the visitor Id. So we are there creating a hash on the already hashed User Id.
tsteur
added
worksforme
The issue cannot be reproduced and things work as intended.
and removed
Bug
For errors / faults / flaws / inconsistencies etc.
labels
May 8, 2018
See https://github.com/matomo-org/matomo/blob/3.5.0-rc1/core/Tracker/Request.php#L830-L832
If the privacy feature introduced in Matomo 3.5.0 is enabled and the userId is hashed with a salt, then the visitorId would still kind of leak the userId. Ideally, when the userId is set and the feature is enabled, then the userId should be salted there as well.
The text was updated successfully, but these errors were encountered: