testssl.sh
tls-scan
| testssl.sh | tls-scan | |
|---|---|---|
| 43 | 2 | |
| 7,713 | 276 | |
| - | - | |
| 8.6 | 4.3 | |
| 2 days ago | about 2 months ago | |
| Shell | C | |
| GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
testssl.sh
-
Badssl.com
You’re in luck because such a tool exists :) https://testssl.sh/
- Testing TLS/SSL Encryption
-
Uncertain how to proceed with patching SSL and TLS issues in MacOS (Sweet32)
Run https://testssl.sh/ and see what ciphers are being offered.
-
Changing SSL Wildcard Certificate
There is https://github.com/drwetter/testssl.sh utility. It can help diagnose issues (e.g. diffs between working and non-working sites).
- Specific SSL Ciphers Test
-
SSL Diag Tool
For internal use, there's https://testssl.sh/
-
Dovecot not offering TLSv1.2 after a few minutes
The current configuration allows for TLSv1 to TLSv1.3 connections. I can verify those using testssl.sh, the tests will succeed (although correctly mentioning, that TLSv1 and TLSv1.1 should be disabled). Running the tests again after about 5 minutes, the results are different. TLSv1.2 now shows "not offered and downgraded to a weaker protocol".
- How to combine pem file and 3 security certificates?
- oggi 2022-11-01 verrà rilasciata una vulnerabilità di livello CRITICAL su OpenSSL 3.0.x
-
alternative to whatsmychaincert.com cli or gui
testssl.sh
tls-scan
-
tls-scan VS trivialscan - a user suggested alternative
2 projects | 25 Apr 2022
-
CryptoLyzer: A comprehensive cryptographic settings analyzer
There are many notable open-source projects (SSLyze, CipherScan, testssl.sh, tls-scan, …) and several SaaS solutions (CryptCheck, CypherCraft, Hardenize, ImmuniWeb, Mozilla Observatory, SSL Labs, …) to do a security setting analysis, especially when we are talking about TLS, which is the most common and popular cryptographic protocol. However, most of these tools heavily depend on one or more versions of one or more cryptographic protocol libraries, like GnuTLS, OpenSSL, or wolfSSL. But why is this such a problem?
What are some alternatives?
https-ssl-cert-check-zabbix - Script to check validity and expiration of TLS/SSL certificate on hosts. May be used with Zabbix or standalone.
sslyze - Fast and powerful SSL/TLS scanning library.
kubernetes-the-hard-way - Bootstrap Kubernetes the hard way. No scripts.
engine - A reference implementation of the Russian GOST crypto algorithms for OpenSSL
ssh-audit - SSH server auditing (banner, key exchange, encryption, mac, compression, compatibility, security, etc)
http-observatory - Mozilla HTTP Observatory
ssh-audit - SSH server & client security auditing (banner, key exchange, encryption, mac, compression, compatibility, security, etc)
ssldump - ssldump - (de-facto repository gathering patches around the cyberspace)
Wazuh - Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
cipherscan - A very simple way to find out which SSL ciphersuites are supported by a target.
OpenSSL - TLS/SSL and crypto library
openssl - UNSUPPORTED Fork of OpenSSL 1.1.1 that includes prototype quantum-resistant algorithms and ciphersuites based on liboqs PLEASE SWITCH TO OQS-Provider for OpenSSL 3