Privacyscanner

Latest version: v0.8.1

Safety actively analyzes 613461 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 4

0.8.0

-----

* GeoIP database download now requires a license key to download. The license
key must be added to the config file of privacyscanner. This is a breaking
change.
* Remove Python 3.5 support. privacyscanner might still run under Python 3.5,
however, we will no longer guarantee that is does in future. Upgrade your
Python to 3.6 or better. This is a breaking change.
* Fix: Host parsing of MX records is now more compliant

0.7.6

-----

* Fix: run\_workers command will no longer run into an infinite loop.
* Fix: Google Analytics detection did not handle the case when aip is not
set correctly.

0.7.5

-----

* Fix: POST data extraction failed under certain circumstances.

0.7.4

-----

* Fix: Also look into POST data for Google Analytics request to find aip=1

0.7.3

-----

* Fix: Check for \_\_utm.gif in Google Analytics check instead of utm.gif
* Fix: Do not consider gtm/js requests as tracking requests for Google
Analytics, since they just load the GTM configuration. This fixes
a bug where a site is mistakenly detected as not using the anonymize IP
extension.
* Start counter for numeric locks at zero instead of one. This makes the
remote debugging ports for Google Chrome used by the "scan" command
consistent with those used the "run\_workers" command.

0.7.2

-----

* Fix: More robust serialization of arguments to the log Javascript function.
This fixes fingeprinting detection with call stacks containing circular
references in the function arguments.
* Fix: Set OpenSSL security level to 0. This will fix some exceptions that
OpenSSL will raise for weak configurations of the server, e.g. small DH key.
* Fix max-age check for HSTS preloading

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.