New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blog posts in the run up to OSCON #257
Comments
Everyone listed above should already have access to the private OCL papers repo. You can use the 'mirage' folder there for work in progress. Hannes, David, would you mind moving your drafts to that folder? |
@amirmc which |
I forgot to actually push my changes. Now done. |
done. |
Looking at how much time we have before the announcements. We realistically have 10 days, with one post per day, starting on 7 July (avoiding weekends, if possible). The first week would be the TLS work, as that's closer to being ready, which leaves the following week for the remainder of the posts. I've just spoken to @yallop and the |
I've started a very rough draft for an Irmin manual in https://github.com/samoht/irmin/blob/docs/doc/manual/manual.pdf?raw=true, which I'll try to turn into a blog post in the next days. |
|
I've pencilled in provisional dates for the remaining posts. Please can @avsm, @jonludlam and @talex5 confirm that the dates are ok. |
The ARM date (draft by 16th) is fine for me. |
Confirmed July 15th fine for me. |
for this monday @avsm wants to setup another (or n other) virtual machines with a cloned fs from tls.openmirage, and configure DNS round robin between these machines. the setup currently does use the socket backend of mirage; and cstruct-1.2.0 (thus without the length checking) |
the article for monday https://github.com/ocamllabs/papers/blob/master/mirage/tls-intro.md is ready from our site.. if someone wants to re-read and look over, please do so. |
Thanks! I'll look over tomorrow just to check language and will commit any tweaks directly. Will comment here when I'm done and will prep a PR for Monday. Are the others going ok? I haven't had a chance to check repo directly. Best wishes, sent via mobile
|
A few comments.
Best, Daniel |
@dbuenzli thanks! I incorporated your suggestions and extended the article with a section on trusted code base https://github.com/ocamllabs/papers/commit/2e2d3263b131a7e48505dee9b71040bacfb1fec3 |
the x509 article https://github.com/ocamllabs/papers/blob/master/mirage/x509.md is also ready for review. I also tested (on a clean system) and adjusted the opam files of the four libraries https://github.com/mirleft/opam-repository |
Le samedi, 5 juillet 2014 à 11:51, Hannes Mehnert a écrit :
|
thanks @dbuenzli https://github.com/ocamllabs/papers/commit/eb95c4116e9e7ba7f652786d3e8d63b84b36f802 -- the reason to link to a specific commit is to not get out of date... |
Le dimanche, 6 juillet 2014 à 09:19, Hannes Mehnert a écrit :
Yes that's what I was suggesting, I didn't realize you were actually doing that... D |
for tomorrow I'd appreciate to have the libraries in opam. in order to do that, I believe there's a mirage release needed as well (due to the entropy story -- most likely with #262 merged). I'm happy to do the set asn1 / nocrypto / mirage-entropy / tls / x509 PRs to opam-repository tomorrow morning (and update the blog post tls-intro to reflect that the releases are there). any outstanding issues (looking at @avsm and @pqwy) which holds us back from releasing the code? the tuesday article is not yet in a good shape, maybe we should move asn and x509 to earlier (@pqwy any status of the asn article?) |
Le dimanche, 6 juillet 2014 à 22:15, David Kaloper a écrit :
|
@dbuenzli Thanks, as always Yes, it's a bit long. I somehow wanted to show the derivation of the library. I'll see if I can cut it down or give more of an outline. In referencing parsing combinators I am both re-tracing my own decision process, and answering a question that comes up (most recently in the meeting with INRIA people). I grounded this derivation in my work with parser combinators. Other people grounded their questions in their familiarity with parser combinators. No people so far mentioned pickler combinators. And similarly, I try to frame any parser I even think of designing in terms of Monads or Applicatives so they at least answer a question I would, personaly, immediately have when reading this article. And in reality, although some people claim the names of those signatures had something to do with CT, we all know they were obtained by blind choice from an unusually big dictionary. And now we're stuck with the names. |
The nocrypto article is ready for a review. I would appreciate any feedback. (Ducks and covers.) |
PRs for opam are in:
and now I'm away from my computer for the rest of the day ;) |
Le lundi, 7 juillet 2014 à 01:49, David Kaloper a écrit :
Well they may not be up to with the fp litterature. I mean basically you are here only rediscovering pickler combinators, it it were an academic paper (is it research or engineering ?) an I were a reviewer, that's a paper I you would make you cite. It surely is nice to try to trace the design process, but in some sense I think you'd need to be more precise (tutorial style) in the derivations that end up not to work so that people really get the feel of why it doesn't work. For myself, while reading that I was like, ok so he didn't know about pickler combinators (which is fine) and he shows us how he rediscovered them, cute.
Best, Daniel |
Le lundi, 7 juillet 2014 à 09:35, Daniel Bünzli a écrit :
Btw. that's the way cmdliner was designed, it's only after the fact that I realized this was an applicative functor. Daniel |
Le lundi, 7 juillet 2014 à 01:50, David Kaloper a écrit :
Best, Daniel |
we revised the article and are happy to get feedback at https://github.com/ocamllabs/papers/blob/master/mirage/tls.md |
Le dimanche, 13 juillet 2014 à 21:56, Hannes Mehnert a écrit :
Comments on the article
Overall an interesting read. It would certainly nice to keep (and update !) the attacks part with the code base. Comments on snippets of code I saw:
Best, Daniel |
One of the series of posts described at: mirage/mirage#257
via @talex5 One of the series of posts described at: mirage/mirage#257
After brief discussion, we decided to swap the order of the last two posts. This give us some more time to try out the ARM work. |
We're supposed to have the release announcement post out on Tues. That post must go up as the link to it is already in the news release. Best wishes, sent via mobile
|
All the posts linked in the news release are at mirage/mirage-www#168 (comment) The only two left to go up are the ARM post and 2.0 announcement. |
That's fine, we can do two posts then I guess. On 19 Jul 2014, at 15:31, Amir Chaudhry notifications@github.com wrote:
|
Yup, will have to be if we want another Irmin post before Tues. I'd say two posts on Tues but they both have to be out before embargo lifts (will double-check what time that is). Best wishes, sent via mobile
|
recap post live at http://openmirage.org/blog/announcing-mirage-20-release |
companion post also live on the Xen Blog at http://blog.xen.org/index.php/2014/07/22/mirage-os-v2-0-the-new-features/ |
We did it! Thank you everyone for the huge effort over the last couple of weeks. All posts are live and we've had a lot of visibility in the meantime, which is fantastic. For reference, you can check out the official press release [1], which links back to the blog posts and is now being picked up by news sites. That means even more people will be finding their way to the content over the coming days and weeks. Great work! [1] http://www.marketwired.com/press-release/xen-project-introduces-new-mirage-os-release-1931602.htm PS you have no idea how much I'm looking forward to clicking the close button. :) |
Congrats, that was nicely coordinated! |
Three cheers for Amir, and all the blog contributors! Now, who's up for a second round of posts?? sound of leaves drifting quietly through a forest On 22 Jul 2014, at 09:25, Thomas Gazagnaire notifications@github.com wrote:
|
@amirmc your blog post doesn't seem to appear on the front page of http://www.xenproject.org/ |
Well spotted. I've pinged Russ about it so hopefully will be fixed soon. Best wishes, sent via mobile
|
We've discussed that we will have a series of blog posts in the run up to OSCON so this issue is to track progress of those posts. This issue will be edited as things change/progress and we pick release dates for those posts. Please don't wait for a prompt to get started :)
All posts should be out by 21 July 2014.
Security by @hannesm and @pqwy
nocrypto
lib - 9 Julyx509
lib - 10 Julyasn1
lib, parsing and unparsing - 11 Julyocaml-tls
API and internals and attacks/mitigations - 14 Julyocaml-tls
andmirage
integration (might not do this one)Others
ctypes
(summary) by @yallop - 15 Julyvchan
by @jonludlam - 16 Julyirmin
by @samoht - 18 Julyirmin in xen(store)
by @djs55 - 21 Julyconduit
by @avsm - 17 July22 July
The text was updated successfully, but these errors were encountered: