BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Pentabarf//Schedule 0.3//EN CALSCALE:GREGORIAN METHOD:PUBLISH X-WR-CALDESC;VALUE=TEXT:Open Source Firmware, BMC and Bootloader devroom X-WR-CALNAME;VALUE=TEXT:Open Source Firmware, BMC and Bootloader devroom X-WR-TIMEZONE;VALUE=TEXT:Europe/Brussels BEGIN:VEVENT METHOD:PUBLISH UID:13528@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220205T110000 DTEND:20220205T111000 SUMMARY:Welome to the Open Source Firmware, BMC and Bootloader devroom DESCRIPTION:
Warm welome to the Open Source Firmware, BMC and Bootloader devroom.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Open Source Firmware, BMC and Bootloader URL:https:/fosdem.org/2022/schedule/2022/schedule/event/welcome_ttosfbabd/ LOCATION:D.firmware ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Daniel Kiper":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:13113@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220205T111000 DTEND:20220205T120000 SUMMARY:Firmware Settings and Menus DESCRIPTION:Among many challanges around initializing hardware, security, and booting intooperating systems, firmware also needs to provide an interface for the user tochange settings, set up a trust anchor, or simply enjoy colorful graphics.This talk summarizes approaches from (U)EFI dating back to 2003,looking at modern OEM UIs in comparison to open implementations such as the menuin webboot, those from System76, EDK2, and Dasharo,and showcasing prototyping environments for further development, finishing witha short discussion of reusable and portable abstractions for designing APIs.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Open Source Firmware, BMC and Bootloader URL:https:/fosdem.org/2022/schedule/2022/schedule/event/fw_settings_and_menus/ LOCATION:D.firmware ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Daniel Maslowski (CyReVolt)":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:13104@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220205T121000 DTEND:20220205T130000 SUMMARY:GRUB - Project Status Update DESCRIPTION:The presentation will discuss current state of GRUB upstream development.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Open Source Firmware, BMC and Bootloader URL:https:/fosdem.org/2022/schedule/2022/schedule/event/grub_status_update/ LOCATION:D.firmware ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Daniel Kiper":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:13101@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220205T131000 DTEND:20220205T133500 SUMMARY:Open Source Firmware status on AMD platforms 2022 DESCRIPTION:This is the 3rd edition of the "Status of AMD platform in coreboot". The talkwill cover the most recent news around the AMD support in open source firmwareecosystem and updates of the topics covered in previous years. We would like topresent status of FSF RYF KGPE-D16 platform revival and related upstreamingeffort, TrenchBoot progress for AMD platforms and status of recent support incoreboot and oreboot projects. Finally we would like to present Dasharo - opensource firmware distribution with long term stable support for older AMDplatforms.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Open Source Firmware, BMC and Bootloader URL:https:/fosdem.org/2022/schedule/2022/schedule/event/osf_on_amd_3rd/ LOCATION:D.firmware ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Michał Żygowski":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:13544@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220205T135000 DTEND:20220205T144500 SUMMARY:OST2: A new way to grow security talent for open source projects DESCRIPTION:In this talk, we'll describe how OpenSecurityTraining2 (OST2) can help grow security talent and awareness on open source projects, and we'll use the coreboot open source firmware as a case study.
Newly structured as a 501c3 non-profit, OST2's core goal is to provide free and open training that helps increase system security. This can take multiple forms, such as training dedicated security engineers, training developers to write more secure code, training potential contributors to security-focused projects, or training engineers on safer alternatives to technologies they're already using. In this talk we'll describe current and future examples of all the previous use cases, and drill deeper into a case study of how 3mbdeb, a licensed service provider for the coreboot open source firmware project, is contributing to OST2 to advance the state of open source firmware security.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Open Source Firmware, BMC and Bootloader URL:https:/fosdem.org/2022/schedule/2022/schedule/event/ost2/ LOCATION:D.firmware ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Piotr Król":invalid:nomail ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Xeno Kovah":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:13218@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220205T151000 DTEND:20220205T161000 SUMMARY:Attestation's Requirements DESCRIPTION:The increased need for secure firmware of all kinds in "IoT" devices from simple sensors to SBC's capable of running large operating systems (eg: Pis, IMXx boards etc) is well known and being driven by many forces, eg: Industry 4.0, 5G, 6G etc. What interestingly is missing is how this firmware provides additional security beyond that of the individual device: to the system as a whole, supply-chain provenance and applications; then further on to how we deal with security incidents through the added forensics and analysis of these devices. Finally we reach the impact of secure firmware to safety-critical systems. Trusted computing, TPM and remote attestation are all well known, but their integration between themselves and the systems they are part of are going to be critical.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Open Source Firmware, BMC and Bootloader URL:https:/fosdem.org/2022/schedule/2022/schedule/event/attestations_requirements/ LOCATION:D.firmware ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Ian Oliver":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:12340@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220205T162000 DTEND:20220205T165000 SUMMARY:Mono Lake Story - how we enabled an open hardware platform DESCRIPTION:We are living in exciting times - we are finally seeing hyperscale server platforms opening up and running on open source software (with caveats still). The journey though is a road full of potholes, braking and sharp turns. Opening up hardware is not easy! Follow along and see how we enabled the Mono Lake platform that was originally created by Facebook (now Meta).
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Open Source Firmware, BMC and Bootloader URL:https:/fosdem.org/2022/schedule/2022/schedule/event/mono_lake_story/ LOCATION:D.firmware ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Sri Ramkrishna":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:13515@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220205T170000 DTEND:20220205T175000 SUMMARY:Plan 9 CPU command, in Go, for Linux DESCRIPTION:I have reimplemented the Plan 9 cpu command in pure Go, available at github.com/u-root/cpu. It uses the ssh transport protocol for data, and the 9p protocol for file system traffic.
If you are used to ssh, cpu will look very similar, to the point of even honoring your .ssh/config! What's different is that when you cpu from your local note to a remote node, file systems of your choosing are visible on the remote node, mounted over 9p, connected to a server running in the cpu command itself. Translation: you don't ever need to talk to a sysadmin to get network mounts set up. Want to use programs from your local node, libraries from your node, and see your home directory? No problem, run with the default namespace. Is the node a different architecture, but you want to use your /home? No problem, just tailor the CPUNAMESPACE variable, e.g.: CPUNAMESPACE=/home:/bin=/arm/bin:/usr=/arm/usr:/lib=/arm/lib cpu cat /proc/cpuinfo. Want all this from power-on/reset? No problem, we embed kernels and a cpu daemon in flash on any of x86, ARM, ARM64, and RISC-V. Want to embed a cpu capability into your Go program? No problem there is a simple package that implements the Go exec.Command interface. Want to understand cpu? No problem, it's easy to read, consisting of 1164 lines of code for the client and 799 for the server.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Open Source Firmware, BMC and Bootloader URL:https:/fosdem.org/2022/schedule/2022/schedule/event/plan_9_cpu_cmd/ LOCATION:D.firmware ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Ron Minnich":invalid:nomail END:VEVENT END:VCALENDAR