May 2022 - Summit-pc - lists.sel4.systems

Fwd: Submission to seL4 Summit - Timing Channels
by June Andronick (seL4 Foundation) 01 Jun '22

01 Jun '22

FYI: ETH can give a talk on hardware support to prevent timing channels. > Begin forwarded message: > > From: "June Andronick (Gmail)" <june.andronick(a)gmail.com> > Subject: Re: Submission to seL4 Summit - Timing Channels > Date: 1 June 2022 at 9:24:50 am AEST > To: Nils Wistoff <nwistoff(a)iis.ee.ethz.ch> > Cc: summit(a)sel4.systems, Gernot Heiser <gernot(a)unsw.edu.au>, Luca Benini <lbenini(a)iis.ee.ethz.ch> > > Hi Nils, > > Thanks for your submission! We’ll come back to you once we’ve worked out the program. > > Cheers > June > >> On 30 May 2022, at 9:01 pm, Nils Wistoff <nwistoff(a)iis.ee.ethz.ch> wrote: >> >> Dear program committee, >> >> Hereby I would like to apply for a presentation at the seL4 summit 2022. >> >> Title: >> Hardware Support for Preventing Microarchitectural Timing Channels >> >> Abstract: >> Microarchitectural timing channels enable information transfer between security domains that are supposed to be isolated, bypassing the operating system's security boundaries. They result from shared microarchitectural state that depends on execution in one security domain and impacts timing in another. Since modern ISAs do not specify timing behaviour, they are insufficient to address these channels. >> >> In this talk, we present fence.t, a novel RISC-V instruction that clears the processor's microarchitectural state and thus any timing dependence on execution history. We show how this instruction was implemented in an open-source RISC-V core and integrated into an experimental version of seL4 with time protection. Furthermore, we will address the challenges of fence.t and its future roadmap. >> >> I am looking forward to your response! >> >> With best regards, >> Nils Wistoff >> >> -- >> Nils Wistoff >> PhD Student >> Integrated Systems Laboratory (IIS) - ETH Zurich >> ETZ J85 >> Gloriastrasse 35 >> CH-8092 Zurich >> +41 44 632 06 75 >> nwistoff(a)iis.ee.ethz.ch >> >

1 0

seL4 summit - another keynote?
by June Andronick (seL4 Foundation) 30 May '22

30 May '22

Dear PC, At the meeting, we have already agreed to have 2 keynotes (Gernot and Boyd) and to have a session on funding agencies, inviting key actors from various countries to give a short brief on their priorities/vision, followed by a discussion. I would also like to have a “Ask Me Anything” session with the Technical Steering Committee. The question is: do we want another keynote and if so who? Before asking the question, I tried to start drafting a program, and given the room configurations and availabilities, it’s already quite packed on the first 2 days where we have the big room. There should still be some flexibility, depending on whether we get the extra “missing” talk we’re enquiring about, but maybe not much if they all accept. So could you please let me know, within a week or earlier, whether you’d like to champion for a specific person/work to be invited for a keynote? If you’re happy with staying with what we already have, please also say it :) NB: I have updated the timeline/planning to reflect the current priorities. In particular we won’t have a meeting to discuss keynote, but we’ll focus on discussing all the items needed to finalise a program https://docs.google.com/spreadsheets/d/1aVK9WoaElkNTL5pXJj-9qJ3GgXkmLV4qwwM… <https://docs.google.com/spreadsheets/d/1aVK9WoaElkNTL5pXJj-9qJ3GgXkmLV4qwwM…> Thanks all June

1 0

(seL4 summit PC) next steps
by June Andronick (seL4 Foundation) 25 May '22

25 May '22

Dear all, Many thanks for the discussion today. Please find attached the master file we worked on this morning. We had a few action items: - Gernot to ask Nils@ETH for a talk (+Q&A) on their hardware on time protection - June to ask HC about a talk on their general plans/roadmap (+ a teaser for the TRENTOS training) - Darren to organise a talk on CASE wrap-up / lessons learned; + potentially a training on the Briefcase tools - Todd to coordinate with John on a talk on HAMR (+ a potential training if available) - Nick to organise a talk on Rust (intro +“Survey”+ potential survey + discussion) - Kent to investigate a talk from Indan Zupanic on MCS virtualisation / MC - Gernot to ask Phil Maker about a talk on LAOT - June to check about a talk from Nathan on FerrOS (unikernel on Rust) - June to investigate a “Funding panel” (NCSC, DARPA, “German DARPA”…) Let me know if I’ve missed anything and please come back to me with an update **early next week** if possible :) I’ll come back to you shortly regarding invited speakers options, once I’ve worked a bit on a program. I think we can do this via email and won’t need another meeting for that. Many thanks all! It’s a pleasure working with such a team :) June

1 0

seL4 summit program and gender diversity
by Ihor Kuz 25 May '22

25 May '22

Hi, I realised after the summit PC meeting that there is very little gender diversity in the program. Does anyone have ideas for what we can do about that? Ihor.

3 2

(seL4 summit) Reviewing instructions - due May 22nd
by June Andronick (seL4 Foundation) 19 May '22

19 May '22

Dear PC, It’s reviewing time! You should all have received a link to your review file (for people on the HCSS PC, this will look familiar; I found the process to work really well so we reused most of it —with the great help from Birg!). As previously said the review process should be really light weight. The aim is to put together an interesting program that we want to listen to or we think others in the community would like to listen to. You’ve all been assigned 6 of the 20 submissions —except Darren and I that will read them all. Feel free to read more (they are really short) and rate them if you want. The allocation is semi-random, and conflict-of-interest (in the reviews and in the live discussion) will be handled quite openly: declare if you have a conflict, but your opinion/knowledge is still welcome. So your job is: 1- read the abstracts you’ve been assigned (or more if you want). 2- rate them in column E (with A+, A, A-, U = Undecided, R = Reject, S = suggest a repurpose (panel, BoF..)). 3- add comments in column F; this is optional but is really useful for (a) you to remember the reasons of your rating in the discussion meeting :) and (b) if you can’t attend the discussion for any reason, we’ll know more about the reasons of your rating. 4- optionally, please tick the theme(s) you think this abstract fits in. 5- while you review, please start thinking about invited speakers, i.e. if some of these talks could be turned into invited talks, or if the topic makes you think about a good invited talk idea from someone else. We will discuss invited talks soon and it’s a good moment to start thinking about it. 6- if reading the reviews makes you think about some seL4 work that has not been submitted but would be a good addition, please let me know. If we agree, I can follow-up to see if they would be happy to participate. And please do all this before end of next week (by 22nd of May) so we have time to collate all the answers before the "PC meeting” (which you should all have received an invitation for). If you have any questions, please don’t hesitate to ask. Many thanks for your work on this, it is very much appreciated :) June

2 3

seL4 Summit Panels
by Robert VanVossen 06 May '22

06 May '22

All, Any thoughts on conducting panels at the seL4 Summit? I was thinking about writing an abstract for a presentation on DornerWorks' experience with mainlining. Focusing on the good pieces, the challenges (which come from our customers, our limited funds, our process, from github, and from the foundation processes), and some thoughts on how to improve. My colleagues thought it could be better as a panel so that we could get perspectives from others in the community, as well as the foundation. I wholly agree with them. So I was wondering if others thought a panel or two would be a good idea. If so, should it still be submitted as an abstract? Thanks, Robbie VanVossen

5 6

Fwd: One week left to propose a talk at the seL4 summit 2022!
by June Andronick (seL4 Foundation) 06 May '22

06 May '22

Dear PC, In addition to the clarifications below, I also want to add that submissions for PC members are welcome (and expected!). I hope to receive submissions from most of you :) Cheers June > Begin forwarded message: > > From: "June Andronick (seL4 Foundation)" <june(a)sel4.systems> > Subject: Re: One week left to propose a talk at the seL4 summit 2022! > Date: 6 May 2022 at 10:02:17 am AEST > To: seL4 Dev List <devel(a)sel4.systems> > > Hi all, > > I have received a number of questions about submissions, so I’m sharing here some answers: > > - The requirements for a talk proposal due next week are (purposefully) light. We only require a short description (few paragraphs) of what the talk will be about. This description will be used by the PC to discuss whether the talk fits well for the submit and should be accepted. > > - The same abstract will also be used later on the website/program to describe each talk. We will give the opportunity to update this description closer to the summit date before publishing it. > > - There is no limit on the number of talks from same company. This may be considered by the PC when discussing acceptance, to allow some balance in the program, but if the topics are different and of interest, there is no intrinsic reason to not accept them all. > > - The last obligation will be to present the talk at the summit :) (preferably in person, else please note in the submission that it will be remote. If you don’t know yet, please indicate it). > > Happy to answer any further questions. Just send them to summit(a)sel4.systems <mailto:summit@sel4.systems> > > Looking forward to your submissions! > > June > >> On 2 May 2022, at 6:05 pm, June Andronick (seL4 Foundation) <june(a)sel4.systems <mailto:june@sel4.systems>> wrote: >> >> A reminder that you have until Monday 9th of May 2022 to propose a talk for the seL4 Summit 2022 :) >> >> http://sel4.systems/news/2022 <http://sel4.systems/news/2022> >> http://sel4.systems/Foundation/Summit/ <http://sel4.systems/Foundation/Summit/> >> http://sel4.systems/Foundation/Summit/cfp <http://sel4.systems/Foundation/Summit/cfp> >> >

1 0