this repo has no description
anil.recoil.org
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-lwt+mirage-kv-lwt+mirage-clock+ptime:installed}%" ]
13 ["ocaml" "pkg/pkg.ml" "build" "--pinned" "%{pinned}%" "--tests" "true"
14 "--with-lwt" "%{lwt+ptime+astring:installed}%"
15 "--with-mirage" "%{mirage-flow-lwt+mirage-kv-lwt+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.6.1" & < "0.7.0"}
32 "cstruct-unix" {with-test & >= "3.0.0"}
33 "ounit" {with-test}
34 "lwt" {>= "2.4.8"}
35 "lwt" {with-test & < "5.0.0"}
36]
37depopts: [
38 "mirage-flow-lwt"
39 "mirage-kv-lwt"
40 "mirage-clock"
41 "ptime"
42 "astring" {with-test}
43]
44conflicts: [
45 "mirage-net-xen" {<"1.3.0"}
46 "mirage-types" {<"3.0.0"}
47 "mirage-kv-lwt" {<"2.0.0"}
48 "sexplib" {= "v0.9.0"}
49 "ppx_sexp_conv" {= "v0.11.0"}
50 "ptime" {< "0.8.1"}
51 "mirage-clock" {>= "3.0.0"}
52]
53
54tags: [ "org:mirage"]
55synopsis: "Transport Layer Security purely in OCaml"
56description: """
57Transport Layer Security (TLS) is probably the most widely deployed security
58protocol on the Internet. It provides communication privacy to prevent
59eavesdropping, tampering, and message forgery. Furthermore, it optionally
60provides authentication of the involved endpoints. TLS is commonly deployed for
61securing web services ([HTTPS](http://tools.ietf.org/html/rfc2818)), emails,
62virtual private networks, and wireless networks.
63
64TLS uses asymmetric cryptography to exchange a symmetric key, and optionally
65authenticate (using X.509) either or both endpoints. It provides algorithmic
66agility, which means that the key exchange method, symmetric encryption
67algorithm, and hash algorithm are negotiated.
68
69Read our [Usenix Security 2015 paper](https://www.usenix.org/conference/usenixsecurity15/technical-sessions/presentation/kaloper-mersinjak).
70"""
71url {
72 src:
73 "https://github.com/mirleft/ocaml-tls/releases/download/0.10.2/tls-0.10.2.tbz"
74 checksum: [
75 "sha256=d5f7deef9445e6d0d877a98a64ba36b610cab3b4bbd01520aff7934611994e7b"
76 "md5=3d7dfafe777c20cf9314eef704c3650b"
77 ]
78}
79authors: [
80 "David Kaloper <david@numm.org>" "Hannes Mehnert <hannes@mehnert.org>"
81]