[SSLSmart] Smart SSL Cipher Enumeration

SSLSmart is a highly flexible and interactive tool aimed at improving efficiency and reducing false positives during SSL testing. A number of tools allow users to test for supported SSL ciphers suites, but most only provide testers with a fixed set of cipher suites. Further testing is performed by initiating an SSL socket connection with one cipher suite at a time, an inefficient approach that leads to false positives and often does not provide a clear picture of the true vulnerability of the server. SSLSmart is designed to combat these shortcomings.

SSLSmart has been tested to work on the following platforms and versions of Ruby:

Windows: Ruby 1.8.6 with wxruby6 (2.0.0) and builder7 (2.1.2).

Linux: Ruby 1.8.7/1.9.1 with wxruby (2.0.0) and builder (2.1.2).

Download SSLSmart

[SSL Audit] Remotely scans web servers for SSL support

SSL Audit remotely scans web servers for SSL support, unlike other tools it is not limited to ciphers supported by SSL engines such as OpenSSL or NSS but can detect all known cipher suites. It features an innovative Fingerprinting engine that was never seen before.

Fingerprint mode (Experimental)

Included is an experimental fingerprint engine that tries to determine the SSL Engine used server side. It does so by sending normal and malformed SSL packets that can be interpreted in different ways. 

SSL Audit is able to fingerprint :

· IIS7.5 (Schannel) 

· IIS7.0 (Schannel) 

· IIS 6.0 (Schannel) 

· Apache (Openssl) 

· Apache (NSS) 

· Certicom 

· RSA BSAFE 

Known issues:· FP on SSLv2 (needs seperated HTTPS request to verify) · No way to export results

Documentation

Download SSL Audit

[SSLDigger v1.02] Tool to assess the strength of SSL

SSLDigger v1.02 is a tool to assess the strength of SSL servers by testing the ciphers supported. Some of these ciphers are known to be insecure.

Features:

• full Browser Support using Microsoft Internet Explorer Browser Control
• support for operating the tool in batch modefor operating on multiple sites simultaneously
• the tool supports reporting in three different formats:XXL,CSV,HTML
• limited support for Server Gated Cryptography.

System Requirements

Windows .NET Framework (can be installed using Windows Update)

Download SSLDigger v1.02

[Harden SSL/TLS] Hardening the SSL/TLS settings

“Harden SSL/TLS” allows hardening the SSL/TLS settings of Windows 2000,2003,2008,2008R2, XP,Vista,7. It allows locally and remotely set SSL policies allowing or denying certain ciphers/hashes or complete ciphersuites. 

This tool specific allows setting policies with regards to what ciphers and protocols are available to applications that use SCHANNEL crypto interface. A lot of windows applications do use this interface, for instance Google Chrome as well as Apple Safari are a few of these. By changing the settings you can indirectly control what ciphers these applications are allowed to use.

Advanced mode 

· re-enable ECC P521 mode on Windows7 and 2008R2

· Set TLS Cache size and timeout

Known issues:· The BETA initialises and sets the OS defaults at startupChangelog :· Fixed Protocol initialization on Vista/Seven/2008/2008R2 (Adrian F. Dimcev) · Fixed TLS 1.1 on Vista/2008 (Reported by Adrian F. Dimcev)

Documentation

Download Harden SSL/TLS

[sslnuke] SSL without verification isn't secure!

We have all heard over and over that SSL without verification is not secure. If an SSL connection is not verified with a cached certificate, it can easily be hijacked by any attacker. So in 2013, one would think we had totally done away with this problem. Browsers cache certificates and very loudly warn the user when a site has offered up a self-verified certificate and should not be trusted, browser vendors have pretty much solved this problem. However, HTTPS is not the only protocol that uses SSL. Unfortunately, many clients for these other protocols do not verify by default and even if they did, there is no guarantee of secure certificate transfer. After all, how many people are willing to pay $50 for an SSL certificate for their FTPS server?

A common protocol that uses SSL but is rarely verified is IRC. Many IRC clients verify by default, but most users will turn this off because IRC servers administrators tend not to purchase legitimate SSL certificates. Some popular clients even leave SSL verification off by default (IRSSI, for example). We already know that this is unwise, any attacker between a user and the IRC server can offer an invalid certificate and decrypt all of the user's traffic (including possibly sensitive messages). Most users don't even consider this fact when connecting to an SSL "secured" IRC server.

The purpose of sslnuke is to write a tool geared towards decrypting and intercepting "secured" IRC traffic. There are plenty of existing tools that intercept SSL traffic already, but most of these are geared towards HTTP traffic. sslnuke targets IRC directly in order to demonstrate how easy it is to intercept "secured" communications. sslnuke usage is simple.

Download sslnuke