Privacyscanner

Latest version: v0.8.1

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

Scan your dependencies

Page 3 of 4

0.5.3

-----

* Fix: testsslsh will only scan if there is actually (START)TLS.
* Fix: mail scan module will add reachable=False key instead of throwing
an exception when the mailserver is not reachable.
* Fix: TLS 1.3 will be detected correctly instead of throwing an exception.

0.5.2

-----

* Use more robust method to terminate Chrome.

0.5.1

-----

* Fix Python3.5 compatibility.
* Add support for older OpenSSL versions in Python.

0.5.0

-----

* Log files are written to dedicated `logs` directory.
* Allow to set options to all scan modules via `__all__` module name.
* Allow to configure `STORAGE_PATH`, where dependencies like GeoIP database
and alike are stored. Defaults to `~/.local/share/privacyscanner`.
* Fix `print_master_config` command.
* The `privacyscanner scan` command can now run concurrently.
* Add `disable_javascript` option to chromedevtools scan module.
* The result key `tls` has been renamed to `https`.
* Rescan a HTTP site with HTTPS if it is available.
* Add information about the HTTP-\>HTTPS and vice versa redirects to the result.
* logger is now available as attribute on a scanning module.
* Add dns module which gathers DNS and GeoIP information for all redirecting
sites up to the final URL and MX records for the site url itself.
* network scan module has been removed, functionality moved to chromedevtools
and the dns scan module.
* Add mail scan module. Gathers some mail functionality and TLS information
about the mailserver.
* Add testsslsh scan module which performs extensive TLS checks using testssl.sh
from Dirk Wetter (https://testssl.sh). These are actually two scan modules:
`testsslsh_https` for HTTPS and `testsslsh_mail` for STMP, sharing the same
code basis.
* Avoid DOM changes during imprint search. This should resolve some exceptions
that occured in that extractor.
* Show error message when dependencies are not installed instead of raising an
exception that bubbles up to the user.
* Try to autodetect Google Chrome on MacOS.
* Users can provide the path to the Google Chrome executable using the
`chrome_executable` scan module option on chromedevtools.
* Add Docker and Docker Compose files to serverleaks scan module.
* Also look for `chromium-browser` to find Chrome (Fedora).

0.4.0

-----

* Use classes for scan modules instead of python modules.
* Improve command line arguments (-c for config, -m for scan modules).
* Add redirect\_chain key to result (chromedevtools).
* Change data structure for requests and responses (chromedevtools).
* Make Debugger resumption more robust (chromedevtools).

0.3.2

-----

* Rebuild packages because 0.3.1 contained some uncomitted changes.

Page 3 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.