mozilla / trackingprotection-tools

A collection of tools for working with and analyzing Tracking Protection as implemented in Firefox

Mozilla Tracking Protection Tools

A collection of tools for working with and analyzing Firefox's Tracking Protection.

Tools

1. DisconnectParser: A python parser for the Disconnect Tracking Protection list.
2. DisconnectReporting: A collection of tools to prepare and send tracking domain reports to Disconnect.

trackingprotection-tools's Issues

Add documentation for the output report format

This is currently documented in a Mozilla-only Google doc (https://docs.google.com/document/d/1n4rNZD9F_W3fSCeRSsA7xWI2ULxP-gnSroH94LrCVyo/edit?usp=sharing), which is outdated. We should update the docs and move them to this repo.

Publish trackingprotection-tools on PyPI

As given in title.

Add tests

An initial set of python 3 and python 2 tests are needed.

Add a helper function to generate valid custom lists

We'd like to generate custom blocklists and entitylists. We should add two helper functions to do so.

Wiki changes

FYI: The following changes were made to this repository's wiki:

• defacing spam has been removed

• Restricting write access to contributors is strongly encouraged. Please make that change (documentation).

These were made as the result of a recent automated defacement of publically writeable wikis.

Drop domains which are public suffixes

The list creation script does this here

Travis CI free usage ends Dec 3; mozilla repos should switch to other CI platforms

We're opening this issue because your project has used Travis CI within the last 6 months. If you have already migrated off it, you can close and ignore this issue.

Travis CI is ending free builds on public repositories. travis-ci.com stopped providingthem in early November, and travis-ci.org will stop after December 31, 2020. To avoid disruptions to your workflows, you must migrate to another CI service.

For production use cases, we recommend switching to CircleCI. This service is already widely used within Mozilla. There is a guide to migrating from Travis CI to CircleCI available here.

For non production use cases, we recommend either CircleCI or Github Actions. There is a guide to migrating from Travis CI to Github Actions available here. Github Actions usage within Mozilla is new, and you will have to work with our github administrators to enable specific actions following this process.

If you have any questions, reach out in #github-admin:mozilla.org on matrix.

Update entity list parsing

About this Issue

There has been update in structure of the entity list following mozilla-services/shavar-prod-lists#223. We should update the entity list parsing here to search for entities key before searching for properties and resources

Acceptance Criteria

• Update _parse_entitylist to search for entities before searching for properties and resources

Add DisconnectReporting

Add utility for building report of domains.

CODE_OF_CONDUCT.md file missing

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

Add a metadata column to `add_observation`

It would be great to be able to attach metadata to the observations in a structured way, such that we have the flexibility to add additional context for some reports. I suggest we simply add an additional parameter to DisconnectReport::add_observation which accepts a json-formatted string.

Add support for pulling in lists by URL

It would be nice to support loading both local files and remote files (by URL).