- If sslscan is compiled on one of these distros, it will not be able to detect SSLv2.
- /sslscan –version looks a bit like
- Added SNI support –sni-name (credit Ken).
- Building on Windows Thanks to a patch by jtesta, sslscan can now be compiled on Windows.
- Compiles if OpenSSL does not support SSLv2 ciphers (merged from digineo/sslscan).
This is a fork of ioerror’s version of sslscan (the original readme of which is included belo…
@s0urc3c0d3err0r: 🍴FORK of @ioerror’s version of #sslscan cc:@KitPloit #webdev #devops #gamedev #indiedev #IoT
This is a fork of ioerror’s version of sslscan (the original readme of which is included below). Changes are as follows:
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 OS X, however this should be considered unsupported. You may need to install any dependencies required to compile OpenSSL from source on OS X. Once you have, just run:
binary (file size, memory consumption, etc.), this allows to enable both SSLv2 and SSLv3 ciphers. In comparison to the method of repackaging the Debian build, this custom OpenSSL build won’t affect other tools on the same system, as they would use the version packaged by the distro’s maintainers.
To compile your own OpenSSL version, you’ll probably need to install the OpenSSL build dependencies:
). For more information on this, see Modifying Build Settings in the OpenSSL wiki.
Kali now ships with a statically built version of sslscan which supports SSLv2.
The package can be found in the Kali Git Repository .
If for whatever reason you can’t install this package, follow the instructions above for statically building against OpenSSL.
is compiled on one of these distros, it will not be able to detect SSLv2.
will still compile (thanks to a patch from digineo/sslscan , based on the debian patch). However, a warning will be displayed in the output to notify the user that SSLv2 ciphers will not be detected.