+1 to use the raw original IP in the fingerprint hash - refs #7667

actually, I remove my +1 - changing this would be a privacy risk. In particular it would let an attacker brute force the md5 hash to get the raw IP address back from the config_id hash, even when IP was anonymised. we cannot leak the IP address in case it was anonymised in Piwik, so we must use the anonimised IP to build the hash.

edit: to brute force the config_id hash, attacker would need Piwik DB + Piwik config (for the salt)

I would have expected to use useAnonymizedIpForVisitEnrichment setting as it is also used for location etc already anyway. I know it is still a different case but I think if someone wants to have complete privacy that person will have disabled that setting anyway.

I would have expected to use useAnonymizedIpForVisitEnrichment setting as it is also used for location etc already anyway.

👍

by default, Piwik users have anonymisation enabled and they use the raw IP

        'useAnonymizedIpForVisitEnrichment' => array('type' => 'boolean', 'default' => false),
        'ipAddressMaskLength'               => array('type' => 'integer', 'default' => 2),

by making the config_id use the raw IP we would improve the tracker detection algorithm that will match many less visitors with colliding config_id

This will improve the detection of visitors in Piwik for the vast majority of Piwik users who use the default privacy settings 👍