No description
Find a file
2012-09-25 08:09:37 +01:00
core Disable optimisation for ghc 7.6.1 to workaround the bad record mac problem 2012-09-25 08:09:37 +01:00
debug fix use of catch to make sure it's usuable on ghc-7.6 and older versions. 2012-09-23 22:54:43 +01:00
extra move testing scripts to the repository's root. 2012-09-25 08:04:18 +01:00
test-scripts always do verbose tests with gnutls-debug-cli 2012-09-25 08:04:37 +01:00
.gitignore filter out .mix 2012-08-27 08:25:08 +01:00
README.md add some debug info 2012-04-20 21:05:46 +01:00
TODO update documentation: TLS1.2 is working 2011-08-17 20:50:57 +01:00

haskell TLS

This library provide native Haskell TLS and SSL protocol implementation for server and client.

Description

This provides a high-level implementation of a sensitive security protocol, eliminating a common set of security issues through the use of the advanced type system, high level constructions and common Haskell features.

Only core protocol available here, have a look at the tls-extra package for default ciphers, compressions and certificates functions.

Features

  • tiny code base (more than 20 times smaller than openSSL, and 10 times smaller than gnuTLS)
  • permissive license: BSD3.
  • supported versions: SSL3, TLS1.0, TLS1.1, TLS1.2.
  • key exchange supported: only RSA.
  • bulk algorithm supported: any stream or block ciphers.
  • supported extensions: secure renegociation, next protocol negotiation (draft 2)

Common Issues

The tools mentioned below are all available from the tls-debug package.

  • Certificate issues

It's useful to run the following command, which will connect to the destination and retrieve the certificate chained used.

tls-retrievecertificate -d <destination> -p <port> -v -c

As an output it will print every certificates in the chain and will gives the issuer and subjects of each. It creates a chain where issuer of certificate is the subject of the next certificate part of the chain:

(subject #1, issuer #2) -> (subject #2, issuer #3) -> (subject #3, issuer #3)

A "CA is unknown" error indicates that your system doesn't have a certificate in the trusted store belonging to any of the node of the chain.