An eMail newsletter privacy analysis framework
privacymail, updated
🕥
2022-01-22 15:01:02
PrivacyMail
PrivacyMail is an eMail privacy analysis system. For more information about the platform, visit privacymail.info.
Installation
PrivacyMail is a Django-based website. The ansible folder contains a deployment script that uses Ansible. See the README in that folder for additional details on what you need to set up to allow the system to deploy correctly. There are also some additional manual steps involved in setting up the necessary cronjobs to automate the retrieval and analysis of eMails. These steps are also described in the README file.
Development
If you want to do some local development, you will need to set up your own privacymail/privacymail/settings.py. See ansible/templates/settings.py for the template. Make sure to replace all statements that look like {{ lookup( [...] ) }}, as these are directives that are interpreted by Ansible during the deployment process.
As a minimum, you will need to set up a virtualenv, install the dependencies from the requirements.txt file, set up the settings file as mentioned above, and provide the system with a Postgres database (docker works fine here). Afterwards, run the database migrations, and you should be good to go. However, in this setup, you will be unable to analyze eMails. For this, you will also need to set up OpenWPM (included as a submodule in this git repository) and configure eMail servers in settings.py. For details on the OpenWPM setup, check the ansible deployment playbook.
License
PrivacyMail is licensed under the GPLv3 license.
Citation
If you use PrivacyMail in a scientific project, please cite our paper at the Annual Privacy Forum 2019:
@article{PrivacyMail,
title = {{Towards Transparency in Email Tracking}},
author = {Maass, Max and Schwär, Stephan and Hollick, Matthias},
journal = {Annual Privacy Forum},
year = {2019}
}
Acknowledgement
The creation of PrivacyMail was funded in part by the DFG as part of project C.1 within the RTG 2050 "Privacy and Trust for Mobile Users".
Issues
Bump node-fetch from 2.6.0 to 3.1.1 in /privacymail/website
opened on 2022-01-22 15:01:01 by dependabot[bot]Bumps node-fetch from 2.6.0 to 3.1.1.
Release notes
Sourced from node-fetch's releases.
v3.1.1
Security patch release
Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred
What's Changed
- core: update fetch-blob by
@jimmywartingin node-fetch/node-fetch#1371- docs: Fix typo around sending a file by
@jimmywartingin node-fetch/node-fetch#1381- core: (http.request): Cast URL to string before sending it to NodeJS core by
@jimmywartingin node-fetch/node-fetch#1378- core: handle errors from the request body stream by
@mdmitry01in node-fetch/node-fetch#1392- core: Better handle wrong redirect header in a response by
@tasinetin node-fetch/node-fetch#1387- core: Don't use buffer to make a blob by
@jimmywartingin node-fetch/node-fetch#1402- docs: update readme for TS
@types/node-fetchby@adamellsworthin node-fetch/node-fetch#1405- core: Fix logical operator priority to disallow GET/HEAD with non-empty body by
@maxshirshinin node-fetch/node-fetch#1369- core: Don't use global buffer by
@jimmywartingin node-fetch/node-fetch#1422- ci: fix main branch by
@dnalborczykin node-fetch/node-fetch#1429- core: use more node: protocol imports by
@dnalborczykin node-fetch/node-fetch#1428- core: Warn when using data by
@jimmywartingin node-fetch/node-fetch#1421- docs: Create SECURITY.md by
@JamieSlomein node-fetch/node-fetch#1445- core: don't forward secure headers to 3th party by
@jimmywartingin node-fetch/node-fetch#1449New Contributors
@mdmitry01made their first contribution in node-fetch/node-fetch#1392@tasinetmade their first contribution in node-fetch/node-fetch#1387@adamellsworthmade their first contribution in node-fetch/node-fetch#1405@maxshirshinmade their first contribution in node-fetch/node-fetch#1369@JamieSlomemade their first contribution in node-fetch/node-fetch#1445Full Changelog: https://github.com/node-fetch/node-fetch/compare/v3.1.0...v3.1.1
v3.1.0
What's Changed
- fix(Body): Discourage form-data and buffer() by
@jimmywartingin node-fetch/node-fetch#1212- fix: Pass url string to http.request by
@serverwentdownin node-fetch/node-fetch#1268- Fix octocat image link by
@lakuapikin node-fetch/node-fetch#1281- fix(Body.body): Normalize
Body.bodyinto anode:streamby@jimmywartingin node-fetch/node-fetch#924- docs(Headers): Add default Host request header to README.md file by
@robertoacevesin node-fetch/node-fetch#1316- Update CHANGELOG.md by
@jimmywartingin node-fetch/node-fetch#1292- Add highWaterMark to cloned properties by
@davesidiousin node-fetch/node-fetch#1162- Update README.md to fix HTTPResponseError by
@thedanfernandezin node-fetch/node-fetch#1135- docs: switch
urltoURLby@dhritzkivin node-fetch/node-fetch#1318- fix(types): declare buffer() deprecated by
@dnalborczykin node-fetch/node-fetch#1345- chore: fix lint by
@dnalborczykin node-fetch/node-fetch#1348- refactor: use node: prefix for imports by
@dnalborczykin node-fetch/node-fetch#1346- Bump data-uri-to-buffer from 3.0.1 to 4.0.0 by
@dependabotin node-fetch/node-fetch#1319- Bump mocha from 8.4.0 to 9.1.3 by
@dependabotin node-fetch/node-fetch#1339- Referrer and Referrer Policy by
@tekwizin node-fetch/node-fetch#1057- Add typing for Response.redirect(url, status) by
@c-win node-fetch/node-fetch#1169- chore: Correct stuff in README.md by
@Jiralitein node-fetch/node-fetch#1361- docs: Improve clarity of "Loading and configuring" by
@serverwentdownin node-fetch/node-fetch#1323- feat(Body): Added support for
BodyMixin.formData()and constructing bodies with FormData by@jimmywartingin node-fetch/node-fetch#1314
... (truncated)
Changelog
Sourced from node-fetch's changelog.
Changelog
All notable changes will be recorded here.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
What's Changed
- core: update fetch-blob by
@jimmywartingin node-fetch/node-fetch#1371- docs: Fix typo around sending a file by
@jimmywartingin node-fetch/node-fetch#1381- core: (http.request): Cast URL to string before sending it to NodeJS core by
@jimmywartingin node-fetch/node-fetch#1378- core: handle errors from the request body stream by
@mdmitry01in node-fetch/node-fetch#1392- core: Better handle wrong redirect header in a response by
@tasinetin node-fetch/node-fetch#1387- core: Don't use buffer to make a blob by
@jimmywartingin node-fetch/node-fetch#1402- docs: update readme for TS
@types/node-fetchby@adamellsworthin node-fetch/node-fetch#1405- core: Fix logical operator priority to disallow GET/HEAD with non-empty body by
@maxshirshinin node-fetch/node-fetch#1369- core: Don't use global buffer by
@jimmywartingin node-fetch/node-fetch#1422- ci: fix main branch by
@dnalborczykin node-fetch/node-fetch#1429- core: use more node: protocol imports by
@dnalborczykin node-fetch/node-fetch#1428- core: Warn when using data by
@jimmywartingin node-fetch/node-fetch#1421- docs: Create SECURITY.md by
@JamieSlomein node-fetch/node-fetch#1445- core: don't forward secure headers to 3th party by
@jimmywartingin node-fetch/node-fetch#1449New Contributors
@mdmitry01made their first contribution in node-fetch/node-fetch#1392@tasinetmade their first contribution in node-fetch/node-fetch#1387@adamellsworthmade their first contribution in node-fetch/node-fetch#1405@maxshirshinmade their first contribution in node-fetch/node-fetch#1369@JamieSlomemade their first contribution in node-fetch/node-fetch#1445Full Changelog: https://github.com/node-fetch/node-fetch/compare/v3.1.0...v3.1.2
3.1.0
What's Changed
- fix(Body): Discourage form-data and buffer() by
@jimmywartingin node-fetch/node-fetch#1212- fix: Pass url string to http.request by
@serverwentdownin node-fetch/node-fetch#1268- Fix octocat image link by
@lakuapikin node-fetch/node-fetch#1281- fix(Body.body): Normalize
Body.bodyinto anode:streamby@jimmywartingin node-fetch/node-fetch#924- docs(Headers): Add default Host request header to README.md file by
@robertoacevesin node-fetch/node-fetch#1316- Update CHANGELOG.md by
@jimmywartingin node-fetch/node-fetch#1292- Add highWaterMark to cloned properties by
@davesidiousin node-fetch/node-fetch#1162- Update README.md to fix HTTPResponseError by
@thedanfernandezin node-fetch/node-fetch#1135- docs: switch
urltoURLby@dhritzkivin node-fetch/node-fetch#1318- fix(types): declare buffer() deprecated by
@dnalborczykin node-fetch/node-fetch#1345- chore: fix lint by
@dnalborczykin node-fetch/node-fetch#1348- refactor: use node: prefix for imports by
@dnalborczykin node-fetch/node-fetch#1346- Bump data-uri-to-buffer from 3.0.1 to 4.0.0 by
@dependabotin node-fetch/node-fetch#1319- Bump mocha from 8.4.0 to 9.1.3 by
@dependabotin node-fetch/node-fetch#1339- Referrer and Referrer Policy by
@tekwizin node-fetch/node-fetch#1057- Add typing for Response.redirect(url, status) by
@c-win node-fetch/node-fetch#1169
... (truncated)
Commits
36e47e83.1.1 release (#1451)5304f3fDon't change relative location header on manual redirect (#1105)f5d3cf5fix(Headers): don't forward secure headers to 3th party (#1449)f2c3d56Create SECURITY.md (#1445)4ae3538core: Warn when using data (#1421)41f53b9fix: use more node: protocol imports (#1428)f674875ci: fix main branch (#1429)1493d04core: Don't use global buffer (#1422)eb33090Chore: Fix logical operator priority (regression) to disallow GET/HEAD with n...7ba5bc9update readme for TS@type/node-fetch(#1405)- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by endless, a new releaser for node-fetch since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/privacymail/PrivacyMail/network/alerts).
Highlight known tracking hosts
opened on 2019-06-05 08:42:19 by malexmaveWe should use existing tracker blocking lists and highlight "known-tracking" hosts in the results. While they have been shown to be incomplete, they are a point to start.
Ensure only valid http[s] links are clicked
opened on 2019-06-04 11:55:55 by malexmaveThe crawler currently also attempts to click whatsapp:// and similar proprietary protocol links. We should ensure that only valid http[s] links are attempted.
3rd party detection on link click incorrect
opened on 2019-05-29 13:51:27 by malexmaveThe 3rd party detection when clicking links is currently a bit flaky. When a newsletter links out to a different page, like Twitter, we try to avoid putting the final destination of the link on the "contacted 3rd parties" list, assuming that users know what they are getting into when clicking such a link.
However, the way this is currently implemented only removes the last request from the log. If the service forwards internally before (i.e. newsletter => http://twitter.com => https://twitter.com), Twitter will still be added as a third party.
Proposed solution: Do not save the request chain to the database directly. Instead, create local objects for each request, and once the end of the chain was reached and we determine that twitter.com should be deleted from the chain, traverse the list backwards and delete all instanced of twitter.com from the chain. Save the remaining requests into the database.
Additional problem: Existing mails already have this artifact in their dataset. We will either need to re-crawl all emails (with all the problems that entails), or write a clean-up script that finds these dangling references and deletes them (without deleting actual tracking stuff). I have one or two ideas on how to achieve that, but will have to play around with it for a while to see if it works.
Analyzer Cronjob occasionally refuses to start
opened on 2019-05-29 10:02:48 by malexmaveThe analyzer cron occasionally refuses to start, not even reaching the first statement of the do() function. Experience has shown that clearing the cache solves this problem. We need to figure out what cache entry causes the problem, and find a way to fix it.