this repo has no description
1opam-version: "2.0"
2homepage: "https://github.com/mirleft/ocaml-tls"
3dev-repo: "git+https://github.com/mirleft/ocaml-tls.git"
4bug-reports: "https://github.com/mirleft/ocaml-tls/issues"
5doc: "https://mirleft.github.io/ocaml-tls/doc"
6maintainer: ["Hannes Mehnert <hannes@mehnert.org>" "David Kaloper <david@numm.org>"]
7license: "BSD-2-Clause"
8
9build: [
10 [ "ocaml" "pkg/pkg.ml" "build" "--pinned" "%{pinned}%" "--tests" "false"
11 "--with-lwt" "%{lwt+ptime:installed}%"
12 "--with-mirage" "%{mirage-flow+mirage-kv+mirage-clock+ptime:installed}%" ]
13 ["ocaml" "pkg/pkg.ml" "build" "--pinned" "%{pinned}%" "--tests" "true"
14 "--with-lwt" "%{lwt+ptime:installed}%"
15 "--with-mirage" "%{mirage-flow+mirage-kv+mirage-clock+ptime:installed}%" ] {with-test}
16 ["ocaml" "pkg/pkg.ml" "test"] {with-test}
17]
18
19depends: [
20 "ocaml" {>= "4.04.2" & < "4.12.0"}
21 "ocamlfind" {build}
22 "ocamlbuild" {build}
23 "topkg" {build}
24 "ppx_sexp_conv"
25 "ppx_deriving"
26 "ppx_cstruct" {>= "3.0.0"}
27 "cstruct" {>= "4.0.0" & < "6.0.0"}
28 "cstruct-sexp"
29 "sexplib"
30 "nocrypto" {>= "0.5.4"}
31 "x509" {>= "0.7.0" & < "0.9.0"}
32 "domain-name" {>= "0.3.0"}
33 "fmt"
34 "cstruct-unix" {with-test & >= "3.0.0"}
35 "ounit" {with-test}
36 "lwt" {>= "2.4.8"}
37 "lwt" {with-test & < "5.0.0"}
38]
39depopts: [
40 "mirage-flow"
41 "mirage-kv"
42 "mirage-clock"
43 "ptime"
44]
45conflicts: [
46 "mirage-kv" {<"3.0.0"}
47 "mirage-flow" {<"2.0.0"}
48 "mirage-clock" {<"3.0.0"}
49 "sexplib" {= "v0.9.0"}
50 "ppx_sexp_conv" {= "v0.11.0"}
51 "ptime" {< "0.8.1"}
52]
53
54tags: [ "org:mirage"]
55synopsis: "Transport Layer Security purely in OCaml"
56description: """\
57
58Transport Layer Security (TLS) is probably the most widely deployed security
59protocol on the Internet. It provides communication privacy to prevent
60eavesdropping, tampering, and message forgery. Furthermore, it optionally
61provides authentication of the involved endpoints. TLS is commonly deployed for
62securing web services ([HTTPS](http://tools.ietf.org/html/rfc2818)), emails,
63virtual private networks, and wireless networks.
64
65TLS uses asymmetric cryptography to exchange a symmetric key, and optionally
66authenticate (using X.509) either or both endpoints. It provides algorithmic
67agility, which means that the key exchange method, symmetric encryption
68algorithm, and hash algorithm are negotiated.
69
70Read our [Usenix Security 2015 paper](https://www.usenix.org/conference/usenixsecurity15/technical-sessions/presentation/kaloper-mersinjak).
71"""
72url {
73 src:
74 "https://github.com/mirleft/ocaml-tls/releases/download/v0.10.5/tls-0.10.5.tbz"
75 checksum: [
76 "sha256=f61f95d62fb70579fe851ed60dbce1ff08e82d188daa999d9ea22b927e7245eb"
77 "md5=57d9477ea79080e9d2485007289cbc5f"
78 ]
79}
80authors: [
81 "David Kaloper <david@numm.org>" "Hannes Mehnert <hannes@mehnert.org>"
82]