On 17 Apr 2015, at 08:17, Hannes Mehnert <[email protected]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hi, > > On 04/17/2015 00:02, Thomas Gazagnaire wrote: >> I've just released mirage 2.4.0 in opam, which goes together with >> conduit 0.8.0, mirage-conduit.2.1.0, tcpip.2.4.0 and >> mirage-http.2.2.0. These releases improve the TLS support, fix ARP >> issues, make the mirage HTTP server signature only depend on >> V1.FLOW and fix some usability issues with the mirage command-line >> tool. > > great! Unfortunately, tcpip-2.4.0 introduces a regression over 2.3.1, > namely not dealing well with trailing bytes, as described by Magnus > Therning on this list. > > Also, the TLS/entropy story is not yet in its final shape (and will be > improved on, see David Kaloper's thread 'update on entropy', and some > discussion in https://github.com/mirage/mirage/pull/390).
I've explicitly disabled Mirage/TLS in Conduit.0.8.2 to make sure it doesn't "escape" before it's ready. You need to pin and modify it to detect TLS for now, so we can prepare the release properly when David finishes the entropy support. -anil _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
