The tls package

[Tags: bsd3, library]

Implementation of the TLS protocol, focusing on purity and more type-checking.

Currently implement only partially the TLS1.0 protocol. Not yet properly secure. Do not yet use as replacement to more mature implementation.


[Skip to ReadMe]

Properties

Versions0.1, 0.1.1, 0.1.2, 0.1.3, 0.2, 0.3, 0.3.1, 0.3.2, 0.3.3, 0.4.0, 0.4.1, 0.5.0, 0.5.1, 0.6.0, 0.6.1, 0.6.2, 0.6.3, 0.6.4, 0.7.0, 0.7.1, 0.7.2, 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.3.1, 0.8.3.2, 0.8.4, 0.8.5, 0.9.0, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 0.9.6, 0.9.7, 0.9.8, 0.9.9, 0.9.10, 0.9.11, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.2.8, 1.2.9, 1.2.10, 1.2.11, 1.2.12, 1.2.13, 1.2.14, 1.2.15, 1.2.16, 1.2.17, 1.2.18, 1.3.0, 1.3.1
Change logNone available
DependenciesAES, base (>=3 && <5), binary (>=0.5), bytestring, certificate (>=0.2), cryptocipher, cryptohash, haskell98, HUnit, mtl, network, QuickCheck (>=2 && <2.3), RSA, spoon, vector [details]
LicenseBSD3
CopyrightVincent Hanquez <vincent@snarc.org>
AuthorVincent Hanquez <vincent@snarc.org>
MaintainerVincent Hanquez <vincent@snarc.org>
Stabilityexperimental
CategoryNetwork
Source repositoryhead: git clone git://github.com/vincenthz/hs-tls
ExecutablesTests, stunnel
UploadedWed Sep 22 17:34:45 UTC 2010 by VincentHanquez
DistributionsDebian:1.2.18, FreeBSD:1.2.8, LTSHaskell:1.2.18, NixOS:1.3.1, Stackage:1.3.1
Downloads101936 total (1807 in last 30 days)
Votes
0 []
StatusDocs uploaded by user
Build status unknown [no reports yet]

Modules

[Index]

Flags

NameDescriptionDefault
testBuild unit testDisabled
executableBuild the executableDisabled

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

Maintainers' corner

For package maintainers and hackage trustees

Readme for tls-0.1.2

The hs-tls project aims to reimplement the full TLS protocol (formely known as SSL) in haskell.
The focus of the projects is to provide a safer implementation than the ones existing,
through more purity, more type-checking, and more units tests.

While the focus is to make it safer than other implementations, this current
implementation is *not* to be considered secure, since it doesn't fully
implement everything necessary (full certificate checking, protocol requirements, etc)