This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "O-Saft"

From OWASP
Jump to: navigation, search
(link to 1st docker container from punkstar removed)
(Docker added)
Line 157: Line 157:
 
* '''Stable Release (18.01.18)''': <u>[https://github.com/OWASP/O-Saft/archive/18.11.18.tar.gz o-saft.tgz]</u>
 
* '''Stable Release (18.01.18)''': <u>[https://github.com/OWASP/O-Saft/archive/18.11.18.tar.gz o-saft.tgz]</u>
 
* more see  [[#Change Log]]
 
* more see  [[#Change Log]]
 +
 +
== Docker ==
 +
A Docker Container can be found at <u>[https://hub.docker.com/r/owasp/o-saft/]</u>
  
 
== News and Events ==
 
== News and Events ==

Revision as of 10:49, 16 April 2018

O-Saft - check for SSL connection, certificate and ciphers(this text to make crawlers happy;-)
Lab big.jpg

O-Saft

OWASP SSL advanced forensic tool / OWASP SSL audit for testers

O-Saft is an easy to use tool to show informations about SSL certificate and tests the SSL connection according given list of ciphers and various SSL configurations.

It's designed to be used by penetration testers, security auditors or server administrators. The idea is to show the important informations or the special checks with a simple call of the tool. However, it provides a wide range of options so that it can be used for comprehensive and special checks by experienced people.

O-Saft is a command-line tool, so it can be used offline and in closed environments. There is also a GUI based on Tcl/Tk. However, it can simply be turned into an online CGI-tool (please read documentation first).

Introduction

Quick Installation
  • Download and unpack o-saft.tgz (Stable Release)
  • to run o-saft: Ensure that following perl modules (and their dependencies) are installed
      IO::Socket::INET, IO::Socket::SSL, Net::SSLeay
      Net::SSLinfo, Net::SSLhello (which are part of the tarball)
  • read and (re-)move o-saft-README
  • Show help
o-saft --help=commands
o-saft --help
  • Start
o-saft +info your.tld
o-saft +check your.tld
o-saft +quick your.tld
o-saft +cipherall your.tld
o-saft +cipherall --starttls=pop3 pop3.your.tld:110
o-saft +info mail.tld:25 --starttls
  • to run the optional checkAllCiphers (tiny program to check solely ciphers, like command '+cipherall'): It usually does not need any perl module to be additionally installed
      Socket (should be part of your perl installation)
      Net::SSLhello (which is part of the tarball)
      NET::DNS (only needed, if option '--mx' is used)
  • Start
checkAllCiphers your.tld
checkAllCiphers --starttls=pop3 pop3.your.tld:110
checkAllCiphers --mx your.tld:25 --starttls=smtp
  • Simple GUI
o-saft.tcl
o-saft.tcl your.tld

Description

The main idea is to have a tool which works on common platforms and can simply be automated.

In a Nutshell
  • show SSL connection details
  • show certificate details
  • check for supported ciphers
  • check for ciphers provided in your own libssl.so and libcrypt.so
  • check for ciphers without any dependency to a library (+cipherall)
  • checks the server's priority for ciphers (+cipherall)
  • check for special HTTP(S) support (like SNI, HSTS, certificate pinning)
  • check for protections against attacks (BEAST, CRIME, DROWN, FREAK, Heartbleed, Lucky 13, POODLE, RC4 Bias, Sweet32 ...)
  • check the length of Diffie Hellman Parameters by the cipher (+cipherall needs option '--experimental')
  • may check for a single attribute
  • may check multiple targets at once
  • can be scripted (headless or as CGI)
  • should work on any platform (just needs perl, openssl optional)
  • can be used in CI / CD environments
  • output format can be customized
  • various trace and debug options to hunt unusual connection problems
  • supports STARTTLS for various protocols like (SMTP, POP3, IMAP, LDAP, RDP, XMPP, IRC (experimental) ...),[without options using openssl]
      slows down to prevent blockades of requests due to too much connections (supported for some protocols like SMTP)
  • Proxy is supported (besides commands using openssl)
  • check of STARTTLS/SMTP for all servers of a MX Resource Record (e.g. checkAllCiphers --mx your.tld:25 --starttls=smtp)
  • checkAllCiphers.pl and '+cipherall' support DTLS for '--experimental' use (if records are *not* fragmented)

New Features of Test Version

Quick Installation (test version)
  • Download and unpack: master.zip
  • Start INSTALL.sh (if you want:)
  • Enjoy new functionality:
  • --starttls='CUSTOM' to customize your own STARTTLS sequence including error handling, see help for '--starttls_phase1..5' and '--starttls_error1..3'
  • '+cipherraw' and 'checkAllCiphers.pl' changed bahavior to check sni (now the default is to use solely sni >=tls1,
    new option --togglesni tests without and with sni in one call
  • checkAllCiphers.pl/+cipherall: shows the length of dh_parameter for ciphers with DHE and DH_anon, shows the elliptic curve that the server prefers for ECDHE (independant from openssl)
  • checkAllCiphers.pl/+cipherall: support of fagmented messages reassembling SSL/TLS-records

What is O-Saft?

O-Saft provides:

  • SSL connection details
  • certificate details
  • full cipher check
  • special HTTP(s) checks
  • check for SSL vulnerabilities
  • can be scripted
  • platfrom independent
  • customizable output
  • supports STARTTLS and Proxy (for most commands)

Screen Shots

Documentation

Presentations

There will be a training O-Saft - TLS/SSL in Practice.
There will be a training TLS/SSL in Practice which in particular covers O-Saft.
There will be a training TLS/SSL in Practice which in particular covers O-Saft. For schedule see here.

(These presentations are in German)

Project Leader

Achim Hoffmann

Licensing

OWASP O-Saft is free to use. It is licensed under the GPL v2 license.

Related Projects

Github

Ohloh

Quick Download

Docker

A Docker Container can be found at [1]

News and Events

  • [12. - 16.06.17] [O-Saft Track] (at OWASP Summit, London)
  • 2013 Top Security Tools
thanks for voting O-Saft as #10 best security tools 2013

In Print / Media

Find a OWASP 24/7 podcast about the tool here.

Classifications

Owasp-labs-trans-85.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files TOOL.jpg
FAQs
  • Where can I get missing Perl-Modules?
    This depends on your OS and Perl installation, but just try cpan <Module-Name>, e.g. cpan Net:DNS
  • I am connected to the internet via a Proxy
    open the cpan-shell using 'cpan' and configure your proxy settings: 'o conf init /proxy/'
  • I can not download the requested files (the proxy needs authentication)
    run 'cpan <Module-Name>' several times, read the error messages and copy the requested files manually to the paths (without any additional temporary extension of the name),
    e.g. http://www.cpan.org/authors/01mailrc.txt.gz => <Your Program Path>/cpan/sources/authors/01mailrc.txt.gz
  • I get the Error "invalid SSL_version specified at .../perl/vendor/lib/IO/Socket/SSL.pm line ..."
  • add options --notlsv13 --nodtlsv1, e.g. perl o-saft.pl +info your.tld --notlsv13 --nodtlsv1
  • use +cipherall to check the ciphers for all protocols
  • My local SSL libraries do *not* support legacy Protocols like SSLv2, SSLv3 or legacy Ciphers
  • use o-saft.pl for all protocols that are supported by your local computer
  • use o-saft.pl +cipherall (or 'checkAllCiphers.pl') to get the ciphers for the missing protocols, or recompile 'Net::SSLeay' and/or openssl to support more protocols and ciphers, see Documentation INSTALLATION for details
  • I can not use the latest features of the test (experimental) version
  • Please verify that you downloaded and unpacked the 'master.zip'-Archive
  • some new functions are protected by the option --experimental, please add it to your command (and take care what happens)
  • o-saft.pl seems to hang
try one or all of following options (see Documentation Performance Problems);
  • --no-dns -no-http --no-cert --no-sni --no-openssl
Acknowledgements

Volunteers

O-Saft is developed by from the contributions of OWASP members. The primary contributors to date have been:

Repository

O-Saft's source code can be found at https://github.com/OWASP/O-Saft .

The latest stable tarball is https://github.com/OWASP/O-Saft/raw/master/o-saft.tgz

Road Map

https://www.owasp.org/index.php/Projects/O-Saft/Roadmap

Involvement in the development and promotion of O-Saft is actively encouraged!

You do not have to be a security expert in order to contribute. Contacts:

Some of the ways you can help:

  • Quality assurance: simply test O-Saft and report defects and strange responses of servers
  • Give some ideas how to implement scoring
  • Need help in implementing
  • authentication for proxies (BASIC, NTLM)
  • check for more SSL/TLS-Extensions (including obsolete ones)
  • check for more vulnerabilities
  • check the full certificate chain

Change Log

  • 16.04.2018 Link Docker Container (pinkstar removed) as docker is supported directly
  • 15.12.2015 Stable Release 15.12.15
  • 15.11.2015 Stable Release 15.11.15
  • 08.01.2015, stable release 15.01.07
  • 05.04.2015, simple GUI available o-saft.tcl
  • 07.12.2014, stable release 14.12.07
  • 16.11.2014, stable release 14.11.14
  • 15.10.2014, check for Poodle vulnerability, see test version: master.zip
  • 10.04.2014 Heartbleed check, see https://github.com/OWASP/O-Saft

Download