
Fast SSL/TLS scanner that discovers supported cipher suites, protocols, and vulnerabilities (Heartbleed, POODLE, CRIME) with certificate chain analysis and key exchange enumeration.
This is a fork of ioerror's version of sslscan (the original readme of which is included below) by rbsec ([email protected]).
Key changes are as follows:
--show-certificate).--failed).--ipv6).--no-compression).--no-ciphersuites.--no-colour.--no-heartbleed).--rdp (credit skettler).--sleep option to pause between requests.--no-preferred.--show-client-cas.--no-cipher-details.--cipher-details.--starttls-ldap.--sni-name (credit Ken).--iana-names--show-certificates--all-groups.It is recommended to ignore the OpenSSL system installation and statically build against your own version. Although this results in a more resource-heavy sslscan binary (file size, memory consumption, etc.), this allows some additional checks such as TLS compression. Note that as of sslscan version 2.2.0, the minimum OpenSSL version required by sslscan is 3.5.0 (LTS), so if your distro ships an older version then building against it will not work, and you will have to do a static build.
To compile your own OpenSSL version, you'll probably need to install the OpenSSL build dependencies. The commands below can be used to do this on Debian.
apt install git zlib1g-dev make gcc
Then run
make static
This will clone the OpenSSL repository, and configure/compile/test OpenSSL prior to compiling sslscan.
Please note: By default, OpenSSL is compiled with gcc without further customization. To compile with clang, install build dependencies using the commands below.
apt install git zlib1g-dev make clang
Then run
make static CC=clang
You can verify whether you have a statically linked OpenSSL version, by checking whether the version listed by sslscan --version has the -static suffix.
Ensure that you local Docker installation is functional, and the build the container with:
make docker
Or manually with:
docker build -t sslscan:sslscan .
You can then run sslscan with:
docker run --rm -ti sslscan:sslscan --help
Thanks to a patch by jtesta, sslscan can now be compiled on Windows. This can either be done natively or by cross-compiling from Linux. See INSTALL for instructions.
Note that sslscan was originally written for Linux, and has not been extensively tested on Windows. As such, the Windows version should be considered experimental.
Pre-build cross-compiled Windows binaries are available on the GitHub Releases Page.
There is experimental support for statically building on macOS (formerly named OS X), however this should be considered unsupported. You may need to install any dependencies required to compile OpenSSL from source on macOS (formerly named OS X). Once you have, just run:
make static
A potentially breaking change has been made to the XML output in version 2.0.0-beta4. Previously, multiple <certificate> elements could be returned (one by default, and a second one if --show-certificate was used).
The key changes are:
<certificates> element that will contain the <certificate> elements.<certificate> elements have a new type attribute, which can either be:
short for the default output.full for when --show-certificate is used.<signature-algorithm> element in a <certificate> no longer contains the "Signature Algorithm:" prefix, or the spacing and newline.If you are using the XML output, then you may need to make changes to your parser.
The short certificate output shows the common name (CN) for subjects and issuers
with exactly one CN. If a name has no CN or multiple CNs, sslscan shows the full
distinguished name instead, so no CN is silently omitted. This applies to both
terminal output and the existing XML subject and issuer elements.
To test this output against local TLS servers without Docker, build sslscan and
run python3 docker_test/test_certificate_names.py. The test needs Python 3 and
an openssl command on PATH; it only connects to loopback addresses.
The bits column in the cipher suite output reports the cipher's effective security strength as returned by OpenSSL, which does not necessarily its encryption key length.
This is most notable in 3DES ciphers (which are listed as 112 bits of effective strength due to the parity bits in the keys and meet-in-the-middle attacks), and in CCM8 ciphers (which are listed as 64 bits of effective strength due to the short authentication tag, as discussed in the upstream OpenSSL pull request).
The same value is written to the bits attribute of each <cipher> in XML output, and the <strength> attribute is a broader consideration of the cipher strength, aligned to the colour in the sslscan output.
This is a fork of sslscan.c to better support STARTTLS.
The original home page of sslscan is:
http://www.titania.co.uk
sslscan was originally written by:
Ian Ventura-Whiting
The current home page of this fork (until upstream merges a finished patch) is:
http://www.github.com/ioerror/sslscan
Most of the pre-TLS protocol setup was inspired by the OpenSSL s_client.c program. The goal of this fork is to eventually merge with the original project after the STARTTLS setup is polished.
Scopri gli strumenti più utilizzati dalla nostra community.
Nessun dato di popolarità ancora.