Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Olivier Levillain <olivier.levillain@ssi.gouv.fr>
Cc: "caml-list@inria.fr List" <caml-list@inria.fr>,
	"cl-mirage@lists.cam.ac.uk List" <cl-mirage@lists.cam.ac.uk>
Subject: Re: [Caml-list] French study on security and functional languages
Date: Fri, 24 May 2013 13:46:30 +0100	[thread overview]
Message-ID: <912F36ED-B157-4DD6-BC68-FFCF99D05E7B@recoil.org> (raw)
In-Reply-To: <519F5FE5.5010504@ssi.gouv.fr>

On 24 May 2013, at 13:41, Olivier Levillain <olivier.levillain@ssi.gouv.fr> wrote:

> Hi everyone,
> 
>> For those reading French, ANSSI (French agency for information
>> security) published a study on security and functional languages, with
>> a set of recommendations. OCaml is apparently well studied:
>>  http://www.ssi.gouv.fr/fr/anssi/publications/publications-scientifiques/autres-publications/lafosec-securite-et-langages-fonctionnels.html
> 
> For information, some of the results have been presented last February
> during the JFLA (Journées francophones des langages applicatifs). The
> slides presented are available on the conference web site
> (http://jfla.inria.fr/2013/programme.html).
> 
	
I was very glad to see the release of the Parsifal code onto Github too:
https://github.com/ANSSI-FR/parsifal

It looks like you have done a lot of the work required towards building
a pure OCaml SSL and Kerberos stack, as well as DNS and SSH parsers in
there too.  We were just discussing the lack of a pure OCaml SSL library
for MirageOS (which already has a full reimplementation of device drivers
and TCP/IP and HTTP, and is just missing the final SSL piece).

best,
Anil

  reply	other threads:[~2013-05-24 12:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24  7:02 David MENTRE
2013-05-24  7:55 ` Francois Berenger
2013-05-24 12:35   ` rixed
2013-05-24 14:43     ` oliver
2013-05-24 15:15       ` rixed
2013-05-27  1:18         ` Francois Berenger
2013-05-24 14:35   ` oliver
2013-05-24 14:59     ` Esther Baruk
2013-05-24 15:05       ` oliver
2013-05-24 15:18       ` David MENTRE
2013-05-24 15:36         ` Esther Baruk
2013-05-24 23:13         ` oliver
2013-05-26 14:14           ` Marek Kubica
2013-05-24 17:44     ` Pierre-Etienne Meunier
2013-05-27  8:55       ` Fabrice Le Fessant
2013-05-24 14:47   ` oliver
2013-05-24 15:02     ` Johan Grande
2013-05-24 12:41 ` Olivier Levillain
2013-05-24 12:46   ` Anil Madhavapeddy [this message]
2013-05-25  8:53     ` Olivier Levillain

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=912F36ED-B157-4DD6-BC68-FFCF99D05E7B@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=cl-mirage@lists.cam.ac.uk \
    --cc=olivier.levillain@ssi.gouv.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