Fingerprinting protection - reason to have different tokens based on sessions

It is not an issue or a bug.
It is a question about the concept of fingerprinting protection.

Description of the issue:
It is a question about fingerprinting protection functionality in brave.
I’ve looked into some of blogs to introduce it and found out that the token for randomization is changed based on sessions and domains.
I have an experience to use other extensions to block canvas fingerprinting based on randomization, but it is not sessions based, and it returns random values for every single request from websites.

Simply, it seems to be safer to return different random values for each request.
Why does brave work based on sessions?

Steps to Reproduce (add as many as necessary): 1. 2. 3.
It is a question about fingerprinting protection, so let me leave it empty.

Actual Result (gifs and screenshots are welcome!):
It is a question about fingerprinting protection, so let me leave it empty.

Expected result:
It is a question about fingerprinting protection, so let me leave it empty.

Reproduces how often:
It is a question about fingerprinting protection, so let me leave it empty.

Operating System and Brave Version(See the About Brave page in the main menu):
It is a question about fingerprinting protection, so let me leave it empty.

1 Like