Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Tor network to send P3A metrics #7341

Open
dionyziz opened this issue Dec 12, 2019 · 0 comments
Open

Use Tor network to send P3A metrics #7341

dionyziz opened this issue Dec 12, 2019 · 0 comments
Labels
feature/tor features/P3A priority/P5 Not scheduled. Don't anticipate work on this any time soon. suggestion
Projects

Comments

@dionyziz
Copy link

In the privacy-preserving product analytics document, it is stated that:

"This combined information — the answer and the version information — is finally sent to Brave’s content delivery network (CDN), operated by Fastly. When an answer reaches the edge of the Fastly CDN, it’s stripped of the IP address and precise timing information."

In particular, this implies that the server at the edge of the Fastly CDN is able to see the IP address of the submitting user. It remains to their capacity to strip the IP address information, as promised in the document, but it also remains in their technical capacity to break the promise of the document and keep a record of the IP address. The promise is not technically ensured.

I recommend that, since Brave already has Tor transport support, the P3A data is sent over the Tor network to Fastly, such that the IP address of the user never reaches the edge of the Fastly CDN and we do not rely on Fastly's or Brave's veracity to ensure the IP address is stripped; instead, through these means we ensure that the technical capacity to record IP addresses is removed completely.

@bsclifton bsclifton added this to ready to implement in P3A Feb 24, 2020
@bsclifton bsclifton moved this from ready to implement to feature requests in P3A Feb 24, 2020
@bsclifton bsclifton moved this from feature requests to backlog in P3A Feb 24, 2020
@rillian rillian self-assigned this Jun 14, 2022
@bsclifton bsclifton added the priority/P5 Not scheduled. Don't anticipate work on this any time soon. label Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/tor features/P3A priority/P5 Not scheduled. Don't anticipate work on this any time soon. suggestion
Projects
P3A
  
backlog
Development

No branches or pull requests

3 participants