Sslyze

Latest version: v6.0.0

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

Scan your dependencies

Page 7 of 12

2.0.2

Not secure
* Bug fixes for scanning servers that support TLS 1.3 (347, 348).
* Added more precise exceptions when the `ServerConnectivityTester` fails to connect to the server (343).
* Added the OpenJDK trust store when validating the server's certificate.

2.0.1

Not secure
* Brought back Windows support (Python 64 bits only).
* Updated OpenSSL to the final 1.1.1 release.
* SSLyze can now be installed via Docker (332).

2.0.0

Not secure
* Only Linux and macOS are supported for this release, but Windows support will be enabled in the next release.
* Dropped support for Python 2 and older versions of Python 3; **only Python 3.6 and 3.7 are supported**.
* Future releases with only support the latest two versions of Python available at the time of the release.
* Added support for the final/official release of TLS 1.3 (RFC 8446).
* The plugin can be tested against Cloudflare: `python -m sslyze --tls_1_3 www.cloudflare.com`
* Added beta support for [TLS 1.3 early data (0-RTT) testing](https://tools.ietf.org/html/draft-ietf-httpbis-replay); see `--early_data` and `EarlyDataScanCommand`.
* The plugin can be tested against Cloudflare: `python -m sslyze --early_data www.cloudflare.com`
* Significantly improved [the documentation for the Python API](https://nabla-c0d3.github.io/sslyze/documentation/).
* Bug fixes (328, 320, 319).
* Switched to a more modern Python tool chain (pipenv, pytest, pyinvoke).
* Removed legacy Python 2/3 code and ported the code base to Python 3 only.

1.4.3

Not secure
* Fixed a bug where the results for OCSP Stapling support would be inconsistent (324).
* Fixed a crash on Python 2.7.

1.4.2

Not secure
* Added the Java trust store as an additional store for validating the server's certificate (287).
* Various bug fixes (312, 313, 314, 315, 316)

1.4.1

Not secure
* Added detection of Symantec-issued certificates when using `--certinfo` or `CertificateInfoScanCommand` (288); such certificates will stop working in future versions of Chrome.
* Bug fixes for when scanning through a proxy.

Page 7 of 12

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.