Daniel Maslowski

Among many challanges around initializing hardware, security, and booting into operating systems, firmware also needs to provide an interface for the user to change 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 menu in webboot, those from System76, EDK2, and Dasharo, and showcasing prototyping environments for further development, finishing with a short discussion of reusable and portable abstractions for designing APIs.

Nach etwas mehr als zehn Jahren Entwicklungszeit der [Befehlssatzarchitektur]( https://en.wikipedia.org/wiki/RISC-V) sind mittlerweile die ersten günstigen [RISC-V Einplatinenrechner](https://riscv.org/exchange/boards/) verfügbar. Was man damit bereits machen kann, wie man dort [Linux](https://kernel.org/) und andere Betriebssysteme ans Laufen bringt durch modernen Code in der [Programmiersprache Rust](https://www.rust-lang.org/) und welche spannenden Projekte drum herum entstanden sind, skizziert dieser Kurzvortrag.

Die Industrie hat hoch automatisierte Prozesse zur Produktion von Elektronik. Wie aber kann der Ansatz des automatisierten De-Assemblements am Ende des Produktlebens funktionieren? Was ist dafür notwendig? Das besprechen wir in dieser Session.

Elektronikschrott ist ein riesen Problem. Recycling findet kaum statt und der Müll wird oft nach Afrika verschickt, wo er die lokale Bevölkerung vergiftet. Beim Splitting des Elektromülls in seine Bestandteile geht es um die Zerlegung in seine Rohstoffbestandteile, aber auch hier ist der Recyclinggrad niedrig. Doch es geht auch anders. Neben der Möglichkeit durch Open-Hardware-Ansätze die Reparierbarkeit von Geräten zu erhöhen und die Langlebigkeit zu gewährleisten, gibt es am End-of-Life eines Produkts die Möglichkeit die Bestandteile auf den Leiterplatten der Hardware abzulöten. Die Industrie hat hoch automatisierte Prozesse zur Produktion von Elektronik. Wie der Ansatz des automatisierten De-Assemblements funktionieren kann und was dafür notwendig ist, besprechen wir in dieser Session.

Other people: Mario Behling Michael Christen Peggy Sylopp

Over the last two years our team has been working on the Pocket Science Lab. While we were connecting with each other online for years the Corona crisis posed a new challenge to us: Chip and component shortages. In this panel we will share our story of how we are tackling this problem and our ideas on how to move forward with local production to solve global delivery issues and reduce the carbon footprint of shipping.

Over the last two years our team has been working on the Pocket Science Lab. While we were connecting with each other online for years the Corona crisis posed a new challenge to us: Chip and component shortages. Even getting prototypes for testing became difficult. In this panel we will share our story of how we are tackling this problem and how the dedication of our community members in Sri Lanka, Sweden, China, India and Germany are essential to overcome difficulties. This session is conceived as a panel where we will also share our ideas about how to move forward with local production to solve global delivery issues and reduce the carbon footprint of shipping. **Panelists**:

• Mario Behling (Facilitator)
• Padmal Madhushanka
• Hong Phuc Dang
• Kee Wee Tang
• Daniel Wessolek
• Daniel Maslowski
• Alessandro Volpato

Other people: Mario Behling Hong Phuc Dang Madhushanka Padmal Alexander Bessmann Kee Wee Tang Daniel Wessolek Alessandro Volpato

With approaches dating back to the 20th century, the idea of a TPM is simple: An isolated, constrained environment to offload trust establishment in a larger computing environment. That implies cryptography, firmware, hardware, and per application, different requirements. This talk elaborates on how the seemingly simple concept has been expanded over the years, enumerating implementations in hardware, firmware, other layers of software, and even web browsers, explaining why it is in fact far more complex than anticipated by looking at contemporary use-cases, ending up with a discussion around the controversy about Microsoft mandating presence of a TPM in order to run Windows 11.

### Advancing from CLIs to GUIs This talk presents the birth of [Fiedka](https://fiedka.app/) out of _utk-web_, a proof of concept image exploration tool that runs on web platforms using WebAssembly. Leveraging [Fiano](https://github.com/linuxboot/fiano)'s `utk`, Fiedka supports firmware developers and analysts through quick navigation and ideas from the web development world, organizing the many different views on the same image in a concise manner. For example, when looking at a typical AMD platform OEM image, there are UEFI and PSP parts. Walking through the challenges of building a suitable graphical interface with a great experience and dealing with specifics, the talk concludes with where Fiedka is at right now and what the next milestones will be, what users can do and try out already, and how to contribute on the various layers of back-end and front-end work as well as conceptual ideas and feature requests.

With the growing demand and support for [LinuxBoot](https://linuxboot.org) in firmware, new approaches to booting operating systems have become possible, based on the Linux [kexec](https://man7.org/linux/man-pages/man8/kexec.8.html) mechanism. This talk walks through the process of creating an environment for booting a large set of different ISOs from various distributions, covering different methods tried and ideas that came up, concluding with how [webboot](https://github.com/u-root/webboot) eventually offers a decent and easy to use interface that can be deployed on a USB stick, tried out in a VM, or even run straight from a mainboard's firmware.

With Intel's Firmware Support Package (FSP) and the recent release of a redistributable firmware binary for the Management Engine, it has become possible to share full firmware images for modern x86 platforms and potentially audit the binaries. Yet, reverse engineering, decompilation and disassembly are still not permitted. However, thanks to previous research, we can have a closer look at the binary data and come to a few conclusions. This talk briefly summarizes the fundamentals of developing custom and open source firmware, followed by a quick guide through the process of analyzing the binaries without actually violating the terms to understand a few bits, and finally poses a statement on the political issues that researchers, repair technicians and software developers are facing nowadays, taking into account how consumers are affected and how they perceive the situtation eventually.

Firmware findet sich in allen Geräten, darunter PCs, Laptops, Netzwerkausstattung, Drucker, eingebettete Geräte wie z.B. in IoT, Industriesteuerungen, Mobiltelefonen, Tablets und mehr. Die Community rund um Open Source Firmware ist in den letzten Jahren gewachsen, so dass sie mehr Austausch in der Entwicklung ermöglicht und Endbenutzer*innen mehr Freiheit schenkt. Bekannte Projekte wie U-Boot, OpenWrt, coreboot, Linuxboot und einige andere zeigen, wie Firmware funktioniert, und sind offen für jede Beteiligung. Dieser Vortrag gibt eine kurze Einführung in Firmware an sich, erklärt den allgemeinen Prozess, sie zu bauen, stellt eine Perspektive auf den aktuellen Entwicklungsstand auf mehreren beliebten Plattformen dar, und schließt mit einem kurzen Endbenutzerbericht ab.