caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Nowak <david.nowak@univ-lille.fr>
To: pip-club@univ-lille.fr, agda@lists.chalmers.se,
	acl2@utlists.utexas.edu, caml-list@inria.fr,
	transform@listes.ifsttar.fr, logic-ml@fos.kuis.kyoto-u.ac.jp,
	jssst-ppl@fos.kuis.kyoto-u.ac.jp,
	"types-announce@lists.seas.upenn.edu"
	<types-announce@LISTS.SEAS.UPENN.EDU>,
	coq-club@inria.fr, gdr-securite.forum@irisa.fr
Subject: [Caml-list] ENTROPY 2019: Call for Participation - Co-located with EuroS&P'19
Date: Tue, 21 May 2019 16:49:52 +0200	[thread overview]
Message-ID: <03CCAC24-6CA5-4F67-B580-B15F4CC1C577@univ-lille.fr> (raw)

***************************************************************
         Call for participation — ENTROPY 2019
     ENabling TRust through Os Proofs … and beYond

                         16 June 2019

Second International workshop on the use of theorem provers for
modelling and verification at the hardware-software interface 

            https://entropy2019.sciencesconf.org

Co-located with EuroS&P'19, KTH, Stockholm, June 2019
***************************************************************

PROGRAM HIGHLIGHTS

Formal Proof of a Secure OS Full Trusted Computing Base
by Dominique Bolignano, Prove & Run

Time protection: principled prevention of timing channels
by Gernot Heiser, University of New South Wales

Proving the security of interrupt handling against interrupt-based side-channel attacks: a case study
by Frank Piessens, KU Leuven

Nailing Down the Architectural Abstraction
by Peter Sewell, University of Cambridge


                 reply	other threads:[~2019-05-21 14:50 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=03CCAC24-6CA5-4F67-B580-B15F4CC1C577@univ-lille.fr \
    --to=david.nowak@univ-lille.fr \
    --cc=acl2@utlists.utexas.edu \
    --cc=agda@lists.chalmers.se \
    --cc=caml-list@inria.fr \
    --cc=coq-club@inria.fr \
    --cc=gdr-securite.forum@irisa.fr \
    --cc=jssst-ppl@fos.kuis.kyoto-u.ac.jp \
    --cc=logic-ml@fos.kuis.kyoto-u.ac.jp \
    --cc=pip-club@univ-lille.fr \
    --cc=transform@listes.ifsttar.fr \
    --cc=types-announce@LISTS.SEAS.UPENN.EDU \
    /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).