From: Hannes Mehnert <hannes@mehnert.org>
To: "caml-list@inria.fr >> Caml-list" <caml-list@inria.fr>
Subject: [Caml-list] [ANN]: tls-0.2, nocrypto-0.2, x509-0.2, asn1-combinators-0.1.1
Date: Thu, 30 Oct 2014 22:15:53 +0100 [thread overview]
Message-ID: <5452AA89.5010800@mehnert.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384
Dear OCaml hackers,
More than 3 months ago we announced the 0.1 release of our TLS library
pack (BSD licensed). Since then we fixed bugs based on user feedback
and also implemented new features.
Now we prepared a pre-halloween special release :)
Highlights (more details are in CHANGES.md of each repository):
- - nocrypto-0.2: uses ctypes, DSA, CCM, compiles on 4.02
- - tls-0.2: epoch exposes information about negotiated session, enum
cleanups (ciphersuites, protocol versions, hash algorithms)
- - asn1-0.1.1: stricter decoding of integers in tags and OIDs,
performance improvements
- - x509-0.2: information about used trust anchor, more utility
functions exported
Read our blog series about the initial release at
http://openmirage.org/blog/introducing-ocaml-tls
An https server in OCaml visualising the TLS handshake
https://tls.openmirage.org
The updated packages are already in opam, opam update && opam upgrade
(or opam install tls/nocrypto/x509/asn1-combinators) should be all you
need to do.
If you encounter any issues, please report these on GitHub
https://github.com/mirleft in the appropriate project.
We're also still looking for code feedback and code reviews.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCQAGBQJUUqqJAAoJELyJZYjffCjuw+UP/jEUlvTxD70kGFU9BwUo2INP
CcvtqSlu+Tn8giKgHx0FwxUEPLw3ugSuADNYsRKyYR4BoJVqMszKdyyN8zZZ6/JT
2vJJjuK8p8N7u8eXuRqS2X4fLsa3k7zKPnnM4y9DL91Z4FJRb6z31TXeQ1Y+u2Zv
aKfyqm68fNUDiN3AKpljDJSAa9WqSAUQD9KV1Uovmr9utl9LsJUCpmxHw73PsvTq
B1EuE+Mu87ZU48r3T1ScxC7WyuMjVmmV6BuwRbZK2yHG0QDUkVT2bA/HxqLKNr7D
lerbCQMVsEGx3rxmPUmnWzIRRB2P31A0aLu1SKYkN7Ex+Y9kp/yQxSc2/+wzrvoK
yBUrt9JJCU55dMsHe4bBvATz3KWLl3Iu2BvuIN9gy8XCKrZM3C0TM2+G5i7vRZCY
DLWbpLMW7uAWVQnl++QMjeP30mqgP4oh3MQGNEVlVWl/rmkuaPmIxJYe9CGVHKwW
JCGA8Go+v/W2hITSmfheG/X/0Uo1I+C318wptMNrAIKb7YZTKxAqbCMGwLCLyVv2
kz7D+RTxVgZLkq4PgCiG1CYhHNf1/8+H0nDbd9eaZaCqfz6RMFguVIElnPqKw2dc
JLirZKbQYq+VxGgqpkDrEE7VIxpFSCJ/3GqCzFFhSC91Ij/IBzxOyqvgGurIIAdN
roNJMHWOi1s4xuiPZcmC
=iL9n
-----END PGP SIGNATURE-----
reply other threads:[~2014-10-30 21:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5452AA89.5010800@mehnert.org \
--to=hannes@mehnert.org \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).