engine
testssl.sh
engine | testssl.sh | |
---|---|---|
1 | 43 | |
351 | 7,655 | |
1.7% | - | |
4.4 | 8.7 | |
about 1 month ago | 8 days ago | |
C | Shell | |
Apache License 2.0 | GNU General Public License v3.0 only |
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.
engine
-
CryptoLyzer: A comprehensive cryptographic settings analyzer
It is not just a theory. A special fork of OpenSSL, maintained by Pluralsight author Peter Mosmans, aims to have as many ciphers as possible. This fork is used and recommended by Mozilla Cipherscan, however, it can offer less than two hundred cipher suites, but there are more than three hundred in the different RFCs according to Cipher Suite Info. The majority of them are weak or insecure, which makes it particularly important to be part of the analysis. In addition, it is also true that there are cipher suites that are not on the Cipher Suite Info list, for instance, Russian standard (GOST) cipher suites. These are rarely used cipher suites, but there is an OpenSSL engine that implements them, so they should be checked.
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
What are some alternatives?
tls-scan - An Internet scale, blazing fast SSL/TLS scanner ( non-blocking, event-driven )
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.
OpenSSL - TLS/SSL and crypto library
ssh-audit - SSH server auditing (banner, key exchange, encryption, mac, compression, compatibility, security, etc)
wolfssl - The wolfSSL library is a small, fast, portable implementation of TLS/SSL for embedded devices to the cloud. wolfSSL supports up to TLS 1.3!
ssh-audit - SSH server & client security auditing (banner, key exchange, encryption, mac, compression, compatibility, security, etc)
openssl - 'Extra featured' OpenSSL with ChaCha20 and Poly1305 support
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.