<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>
    </p>
    <div class="moz-text-flowed"
      style="font-family: -moz-fixed; font-size: 14px;" lang="x-unicode">A
      web version of this CFP is available at: <a
        class="moz-txt-link-freetext"
        href="https://falder.org/fosdem25-cfp">https://falder.org/fosdem25-cfp</a>
      <br>
      <br>
      # Confidential Computing devroom @ FOSDEM 2025
      <br>
      <br>
      Following the success of [last years' editions](<a
        class="moz-txt-link-freetext"
href="https://archive.fosdem.org/2024/schedule/track/confidential-computing/">https://archive.fosdem.org/2024/schedule/track/confidential-computing/</a>),
      we are for the 6th time organizing a devroom devoted to the
      emerging open-source ecosystem around *hardware-based Trusted
      Execution Environments (TEEs)*, which nowadays is also known under
      the term <b class="moz-txt-star"><span class="moz-txt-tag">*</span>confidential
        computing<span class="moz-txt-tag">*</span></b>.<br>
      <br>
      Confidential computing leverages hardware-based TEEs in order to
      protect and secure data in-use. This devroom is devoted to this
      emerging free and open-source ecosystem around TEEs that allow to
      directly isolate and attest trusted "enclave" software components
      running on top of a potentially compromised operating system. Over
      the last years, all major processor vendors have developed some
      form of TEE support, e.g.,
      <br>
      <br>
      * ARM TrustZone, Morello & Confidential Computing Architecture
      (CCA)
      <br>
      * AMD Secure Encrypted Virtualization (SEV) & SEV-ES/SEV-SNP
      extensions
      <br>
      * IBM Secure Execution for Linux on Z (SEL).
      <br>
      * Intel Software Guard Extensions (SGX) and Trust Domain
      Extensions (TDX)
      <br>
      * NVIDIA H100 GPUs
      <br>
      <br>
      Hence, with today's mainstream consumer hardware being
      increasingly shipped with these advanced trusted computing
      technologies, this devroom wants to foster discussion on the
      much-needed free and open-source TEE ecosystem amongst industry
      players, academics, enthusiasts, hobbyists, and project
      maintainers.
      <br>
      <br>
      <br>
      ## Desirable topics
      <br>
      <br>
      The devroom's topics of interest include, but are not limited to:
      <br>
      <br>
      * Open-source confidential computing.
      <br>
      * An introduction to the existing solutions and the use cases they
      cover, etc.
      <br>
      * Programming frameworks for TEEs: how to develop free and
      open-source
      <br>
        software that can run inside enclaves (e.g., library OSs, SDKs,
      Linux
      <br>
        kernel support, etc.).
      <br>
      * Confidential computing deployment: Challenges and benefits.
      <br>
      * Use cases and applications on top of TEEs such as applying
      <br>
        confidential computing to the Cloud Native space.
      <br>
      * Compiler and language support for emerging trusted hardware
      extensions.
      <br>
      * Open-source enclave processor designs (e.g., RISC-V TEEs).
      <br>
      * Attestation, focusing on Confidential Computing (see note below)
      <br>
      * Existing technologies:
      <br>
         * What do they have in common, how do they differ?
      <br>
         * Which confidential computing use cases can they cover?
      <br>
      * Upcoming technologies:
      <br>
         * TEEs on accelerators (GPUs, NPUs, DPUs, etc)
      <br>
         * Interaction between existing and upcoming technologies
      <br>
         * Opportunities
      <br>
      * Vision: future TEEs (what is missed, proposals, wishes,
      discussions).
      <br>
      * TEE-specific attacks and defenses: reverse engineering,
      side-channels,
      <br>
        vulnerabilities, exploits.
      <br>
      <br>
      ## This year's changes
      <br>
      <br>
      As there's a dedicated [attestation devroom](<a
        class="moz-txt-link-freetext"
        href="https://fosdem.org/2025/schedule/track/attestation/">https://fosdem.org/2025/schedule/track/attestation/</a>),
      we encourage topics related to
      <br>
      attestation that do not relate to general confidential computing
      to be
      <br>
      submitted there.
      <br>
      <br>
      Please note that we do **not** allow remote speakers this year
      anymore. All speakers need to commit to be at FOSDEM in-person on
      February 1, 2025 in Brussels, Belgium.
      <br>
      <br>
      ## Key dates (Brussels time)
      <br>
      <br>
      * Submission deadline: December 1, 2024
      <br>
      * Announcement of selected talks: December 15, 2024 or earlier
      <br>
      * FOSDEM dates February 1 & 2, 2025
      <br>
      * Confidential computing devroom date: February 1, 2025, 9am-1pm
      <br>
      <br>
      ## Submit a talk proposal
      <br>
      <br>
      Submissions are required to proceed through the [new and updated
      FOSDEM
      <br>
      2025 system](<a class="moz-txt-link-freetext"
        href="https://pretalx.fosdem.org/fosdem-2025/cfp">https://pretalx.fosdem.org/fosdem-2025/cfp</a>).
      <br>
      <br>
      Your submission must include the following information:
      <br>
      <br>
      * Proposal title of your talk: please be descriptive, as the
      audience
      <br>
      will have to choose to attend your talk out of a listing with ~500
      talks
      <br>
      from other projects at FOSDEM.
      <br>
      * Select "Confidential computing devroom" as the track.
      <br>
      * A longer description if you wish to do so.
      <br>
      * A short abstract of one paragraph.
      <br>
      * Submission notes to let us know of specifics to your talk.
      <br>
      * Additional speakers if you want to add them.
      <br>
      * FOSDEM requires you to fill in which open-source license you use
      and
      <br>
      to provide links to your source code. *All our talks at FOSDEM
      **must** be
      <br>
      about free and open-source software, so please make it clear to
      the
      <br>
      organizers by providing a public URL to the source code of the
      relevant
      <br>
      project(s).In case the URL is not yet public, please indicate so
      and
      <br>
      explicitly clarify your commitment to have the code available the
      latest
      <br>
      at the time of the devroom.*
      <br>
      * Information about yourself.
      <br>
      <br>
      We target a block of **20 minutes** per talk (<b
        class="moz-txt-star"><span class="moz-txt-tag">*</span>including<span
          class="moz-txt-tag">*</span></b> ~5 minutes of Q&A).
      <br>
      <br>
      If you wish to only give a shorter talk, you can let us know in
      the
      <br>
      submission notes. We leave the option open to have several **10
      minute**
      <br>
      talks for rapid-fire ideas and discussion points. Let us know in
      the
      <br>
      submission notes if you plan your submission to be more
      interactive so
      <br>
      that we can plan in more time for discussion after your talk.
      <br>
      <br>
      ## Useful links
      <br>
      <br>
      * [FOSDEM 2025 website](<a class="moz-txt-link-freetext"
        href="https://fosdem.org/2025/">https://fosdem.org/2025/</a>)
      <br>
      * [FOSDEM 2024 Confidential Computing devroom](<a
        class="moz-txt-link-freetext"
href="https://archive.fosdem.org/2024/schedule/track/confidential-computing/">https://archive.fosdem.org/2024/schedule/track/confidential-computing/</a>)
      <br>
      * [FOSDEM 2023 Confidential Computing devroom](<a
        class="moz-txt-link-freetext"
href="https://archive.fosdem.org/2023/schedule/track/confidential_computing/">https://archive.fosdem.org/2023/schedule/track/confidential_computing/</a>)
      <br>
      * [FOSDEM 2022 Hardware-Aided Trusted Computing devroom](<a
        class="moz-txt-link-freetext"
href="https://archive.fosdem.org/2022/schedule/track/hardware_aided_trusted_computing/">https://archive.fosdem.org/2022/schedule/track/hardware_aided_trusted_computing/</a>)
      <br>
      * [FOSDEM 2021 Hardware-Aided Trusted Computing devroom](<a
        class="moz-txt-link-freetext"
href="https://archive.fosdem.org/2021/schedule/track/hardware_aided_trusted_computing/">https://archive.fosdem.org/2021/schedule/track/hardware_aided_trusted_computing/</a>)
      <br>
      * [FOSDEM 2020 Hardware-Aided Trusted Computing devroom](<a
        class="moz-txt-link-freetext"
href="https://archive.fosdem.org/2020/schedule/track/hardware_aided_trusted_computing/">https://archive.fosdem.org/2020/schedule/track/hardware_aided_trusted_computing/</a>)
      <br>
      <br>
      ## Contact and organizers
      <br>
      <br>
      If you have any questions, feel free to reach out to the whole
      organizer team under <a class="moz-txt-link-freetext"
        href="mailto:confidential-devroom-manager@fosdem.org">mailto:confidential-devroom-manager@fosdem.org</a>
      or reach an individual organizer below:
      <br>
      <br>
      * Organizers:
      <br>
        * [Fabiano Fidêncio](<a class="moz-txt-link-freetext"
        href="mailto:fabiano@fidencio.org">mailto:fabiano@fidencio.org</a>)
      <br>
        * [Fritz Alder](<a class="moz-txt-link-freetext"
        href="mailto:fritz.alder.work@gmail.com">mailto:fritz.alder.work@gmail.com</a>)
      <br>
        * [Ilaria Battiston](<a class="moz-txt-link-freetext"
        href="mailto:ilaria.battiston@cwi.nl">mailto:ilaria.battiston@cwi.nl</a>)
      <br>
        * [Jo Van Bulck](<a class="moz-txt-link-freetext"
        href="mailto:jo.vanbulck@kuleuven.be">mailto:jo.vanbulck@kuleuven.be</a>)
      <br>
        * [Steffen Eiden](<a class="moz-txt-link-freetext"
        href="mailto:fosdem@eiden.de">mailto:fosdem@eiden.de</a>)
      <br>
      <br>
    </div>
  </body>
</html>