Chaos Computer Club - archive feed

In recent years the amount of vulnerabilities and also the amount of systems, installations or containers a single sysadmin has to oversee has grown beyond any human capable measures. The best help here is more automation in various places, which needs to be driven by automation consumable data. We will look at two primary areas, the automation data provided by SUSE for security fixes and also very fresh the inventory data, or "Software Bill of Materials (SBOM)". The talk will go over various formats, what SUSE offers and their purposes and also give some future look out on more improved or even more automation data formats. In recent years the amount of vulnerabilities and also the amount of systems, installations or containers a single sysadmin has to oversee has grown beyond any human capable measures. The best help here is more automation in various places, which needs to be driven by automation consumable data. We will look at two primary areas, the automation data provided by SUSE for security fixes and also very fresh the inventory data, or "Software Bill of Materials (SBOM)". The talk will go over various formats, what SUSE offers and their purposes and also give some future look out on more improved or even more automation data formats. about this event: https://c3voc.de

This presentation gives an overview of application design and development for Kubernetes, the de facto standard for container orchestration in enterprises of all sizes. Using a small web server code base as an example, the talk outlines the complete application lifecycle from the initial design to deployment, service-based access in addition to more advanced aspects such as scalability, resilience and high availability. The focus of this presentation is not so much on theory but rather practice using a live environment to demonstrate concepts and illustrate principles. Overview of the talk: - Application code base: The guinea pig - Packaging: Image building and registry management - Deployment: Populating the cluster - Services: Internal and external network access - High availability & resilience: Planning for the worst and beyond - Advanced concepts: Load balancers, Ingress and more - Spin your own: Kubernetes on a budget - Discussion & Q&A The presentation assumes a basic understanding of Docker and Kubernetes in addition to fundamental aspects of application design and programming. This presentation gives an overview of application design and development for Kubernetes, the de facto standard for container orchestration in enterprises of all sizes. Using a small web server code base as an example, the talk outlines the complete application lifecycle from the initial design to deployment, service-based access in addition to more advanced aspects such as scalability, resilience and high availability. The focus of this presentation is not so much on theory but rather practice using a live environment to demonstrate concepts and illustrate principles. Overview of the talk: - Application code base: The guinea pig - Packaging: Image building and registry management - Deployment: Populating the cluster - Services: Internal and external network access - High availability & resilience: Planning for the worst and beyond - Advanced concepts: Load balancers, Ingress and more - Spin your own: Kubernetes on a budget - Discussion & Q&A The presentation assumes a basic understanding of Docker and Kubernetes in addition to fundamental aspects of application design and programming. about this event: https://c3voc.de

OpenSUSE MicroOS, SLE Micro and the SUSE Adaptable Linux Platform (ALP) have moved to using SELinux for Mandatory Access Control (MAC). There are some key differences between a traditional Linux system without MAC, and one with SELinux. Furthermore, using SELinux on transactional systems such as openSUSE MicroOS and ALP-based distributions has its own peculiarities. In this talk we will introduce SELinux, describe what it does, and show how to work with it. We will then see how it's used on a transactional immutable system such as an ALP-based distribution, where most workloads are run inside containers. This talk is for a beginner to intermediate-level audience. You should have a general understanding of both traditional and immutable Linux systems, but won't need specific SELinux expertise. OpenSUSE MicroOS, SLE Micro and the SUSE Adaptable Linux Platform (ALP) have moved to using SELinux for Mandatory Access Control (MAC). There are some key differences between a traditional Linux system without MAC, and one with SELinux. Furthermore, using SELinux on transactional systems such as openSUSE MicroOS and ALP-based distributions has its own peculiarities. In this talk we will introduce SELinux, describe what it does, and show how to work with it. We will then see how it's used on a transactional immutable system such as an ALP-based distribution, where most workloads are run inside containers. This talk is for a beginner to intermediate-level audience. You should have a general understanding of both traditional and immutable Linux systems, but won't need specific SELinux expertise. about this event: https://c3voc.de

Showing cross building our new code base, based on openSUSE Factory. This includes: * Cross architecture package builds * Cross architecture image builds * Cross OS Container builds All covered by Open Build Service or plain git and pbuild tooling locally using the same sources. Showing cross building our new code base, based on openSUSE Factory. This includes: * Cross architecture package builds * Cross architecture image builds * Cross OS Container builds All covered by Open Build Service or plain git and pbuild tooling locally using the same sources. about this event: https://c3voc.de

For the administrator of many Linux machines, [Uyuni](https://www.uyuni-project.org) is a very important tool. It currently runs on premise in a virtual machine or on bare metal. Could it be running in the kubernetes cluster of the lab? Would it be more scalable? Would I finally get high availability or resilience for it? This session will address these questions by explaining how we got Uyuni running in [K3S](https://k3s.io/) on ALP. We will also see which of the container-ready applications benefits would apply and what could be the next steps towards a more modern application. For the administrator of many Linux machines, [Uyuni](https://www.uyuni-project.org) is a very important tool. It currently runs on premise in a virtual machine or on bare metal. Could it be running in the kubernetes cluster of the lab? Would it be more scalable? Would I finally get high availability or resilience for it? This session will address these questions by explaining how we got Uyuni running in [K3S](https://k3s.io/) on ALP. We will also see which of the container-ready applications benefits would apply and what could be the next steps towards a more modern application. about this event: https://c3voc.de

After 13 years, a new major release of the syslog-ng logging application is available. Syslog-ng 4.0 brings type support and many additional enhancements. This presentation also gives you an overview of some of the larger features since the previous major release, and then proves why type support is a major enhancement, improving both operations and security. In version 3 and earlier, syslog-ng handled all data as text. Syslog-ng 4 can associate the proper type information with data parsed from log messages using the JSON or PatternDB parsers. You can use type information for comparisons within syslog-ng, and storing data to various destinations, like Elasticsearch or MongoDB. Type support enables more precise filtering and thus real-time security alerting in syslog-ng, and easier searching and reporting in databases. I give a quick overview of the major new syslog-ng features during the version 3 series, including disk-buffer, message parsing, Python support, HTTP destination, Kubernetes support and how these combined with 4.0 features improve both operations and security. After 13 years, a new major release of the syslog-ng logging application is available. Syslog-ng 4.0 brings type support and many additional enhancements. This presentation also gives you an overview of some of the larger features since the previous major release, and then proves why type support is a major enhancement, improving both operations and security. In version 3 and earlier, syslog-ng handled all data as text. Syslog-ng 4 can associate the proper type information with data parsed from log messages using the JSON or PatternDB parsers. You can use type information for comparisons within syslog-ng, and storing data to various destinations, like Elasticsearch or MongoDB. Type support enables more precise filtering and thus real-time security alerting in syslog-ng, and easier searching and reporting in databases. I give a quick overview of the major new syslog-ng features during the version 3 series, including disk-buffer, message parsing, Python support, HTTP destination, Kubernetes support and how these combined with 4.0 features improve both operations and security. about this event: https://c3voc.de

Let's talk about the current state and ongoing plans with openSUSE Leap 16.0 which is based on SUSE's Adaptable Linux Platform. Let's talk about the current state and ongoing plans with openSUSE Leap 16.0 which is based on SUSE's Adaptable Linux Platform. about this event: https://c3voc.de

Is the IBM mainframe really an old legacy system? If all people are speaking about Cloud Native, Edge Computing and Industry 4.0, IBM has released a new mainframe exactly for the combination with that all. You can integrate the new "small" mainframe as a "Thing" or IoT device into manufacturing facilities or use it in for smaller company requirements for processing a lot of tasks/instructions in parallel. Then you can combine it with the Public Cloud or Embedded Systems. You will receive an overview, what is possible today with mainframes by IBM. Is the IBM mainframe really an old legacy system? If all people are speaking about Cloud Native, Edge Computing and Industry 4.0, IBM has released a new mainframe exactly for the combination with that all. You can integrate the new "small" mainframe as a "Thing" or IoT device into manufacturing facilities or use it in for smaller company requirements for processing a lot of tasks/instructions in parallel. Then you can combine it with the Public Cloud or Embedded Systems. You will receive an overview, what is possible today with mainframes by IBM. about this event: https://c3voc.de

A quick overview of the upcoming RPM 4.19 release and the plans beyond that. A quick overview of the upcoming RPM 4.19 release and the plans beyond that. about this event: https://c3voc.de

This talk will introduce the new zypper-keys plugin. It provides an easy way to manage rpm repo signing keys on your local system. [https://github.com/asdil12/zyppkeys](https://github.com/asdil12/zyppkeys) This talk will introduce the new zypper-keys plugin. It provides an easy way to manage rpm repo signing keys on your local system. [https://github.com/asdil12/zyppkeys](https://github.com/asdil12/zyppkeys) about this event: https://c3voc.de

When using **Xorg**, in order to have a headless remote session we could use **Xvnc**, and it worked great. You can start with it a headless **Xorg** display, on top of it use any desktop environment or just run a **Xorg** client and access it using **VNC** protocol. Now with **Wayland**, the display server is also the windows manager/compositor so there isn't just one single display server to use any desktop environment but each desktop environment has its own **Wayland** compositor implementation. In this talk, I will explain my quest to have a **Wayland** headless remote desktop using the **RDP** protocol in the **GNOME** environment. Most of the work I'm doing is on this [MR](https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/139). When using **Xorg**, in order to have a headless remote session we could use **Xvnc**, and it worked great. You can start with it a headless **Xorg** display, on top of it use any desktop environment or just run a **Xorg** client and access it using **VNC** protocol. Now with **Wayland**, the display server is also the windows manager/compositor so there isn't just one single display server to use any desktop environment but each desktop environment has its own **Wayland** compositor implementation. In this talk, I will explain my quest to have a **Wayland** headless remote desktop using the **RDP** protocol in the **GNOME** environment. Most of the work I'm doing is on this [MR](https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/139). about this event: https://c3voc.de

This should consist of nine short 4-minute talks by users with 1 minute for handover. Users do not need their own laptop, but instead link their resources on https://etherpad.opensuse.org/p/lightning-talks-osc2023 Topics can be - a project the presenter made or uses that might be useful to other Geekos - a relevant topic where you look for others to join a discussion - etc This should consist of nine short 4-minute talks by users with 1 minute for handover. Users do not need their own laptop, but instead link their resources on https://etherpad.opensuse.org/p/lightning-talks-osc2023 Topics can be - a project the presenter made or uses that might be useful to other Geekos - a relevant topic where you look for others to join a discussion - etc about this event: https://c3voc.de

Everybody of us have got a laptop. Then there are some Embedded enthusiasts with arm hardware. Did you hear already about the architecture s390x for mainframes, which includes IBM zSystems and LinuxONE? You will learn, where such hardware is used and that you can also still use it with openSUSE. Hints will be given, how to receive mainframe access for free for open source development. Finally, there is a short introduction, how you can be included for better s390x support (with feedback) within the Linux Distributions Working Group at the Open Mainframe Project. Everybody of us have got a laptop. Then there are some Embedded enthusiasts with arm hardware. Did you hear already about the architecture s390x for mainframes, which includes IBM zSystems and LinuxONE? You will learn, where such hardware is used and that you can also still use it with openSUSE. Hints will be given, how to receive mainframe access for free for open source development. Finally, there is a short introduction, how you can be included for better s390x support (with feedback) within the Linux Distributions Working Group at the Open Mainframe Project. about this event: https://c3voc.de

systemd-boot is a rather simple UEFI boot manager. Using it instead of grub might be desirable in the future. The combination with btrfs snapshots makes things more complicated though. This talk gives an introduction to systemd-boot and the challenges to fully integrate it into openSUSE. systemd-boot is a rather simple UEFI boot manager. Using it instead of grub might be desirable in the future. The combination with btrfs snapshots makes things more complicated though. This talk gives an introduction to systemd-boot and the challenges to fully integrate it into openSUSE. about this event: https://c3voc.de

BCI (Base Container Images) is a set of open-source container images that developers and operators can use as a foundation for containerizing applications. BCIs cover a wide range of use cases and scenarios compared to traditional enterprise distribution images. We had to take a different approach to testing and delivery to cover all these new use cases. In this session we briefly cover the history of the Base Container Images and the tooling that we created in the process. This includes our [Dockerfile generator](https://github.com/SUSE/BCI-dockerfile-generator), the [BCI test suite](https://github.com/SUSE/BCI-tests/), and the [`pytest_container`](https://github.com/dcermak/pytest_container) plugin. We also take a look how we moved the development from our internal build service to the [public Open Build Service](https://build.opensuse.org/project/subprojects/devel:BCI) and then to [Github](https://github.com/SUSE/BCI-dockerfile-generator). BCI (Base Container Images) is a set of open-source container images that developers and operators can use as a foundation for containerizing applications. BCIs cover a wide range of use cases and scenarios compared to traditional enterprise distribution images. We had to take a different approach to testing and delivery to cover all these new use cases. In this session we briefly cover the history of the Base Container Images and the tooling that we created in the process. This includes our [Dockerfile generator](https://github.com/SUSE/BCI-dockerfile-generator), the [BCI test suite](https://github.com/SUSE/BCI-tests/), and the [`pytest_container`](https://github.com/dcermak/pytest_container) plugin. We also take a look how we moved the development from our internal build service to the [public Open Build Service](https://build.opensuse.org/project/subprojects/devel:BCI) and then to [Github](https://github.com/SUSE/BCI-dockerfile-generator). about this event: https://c3voc.de

We are using SALT to deploy SUSE Systems for production. The included modules work well for usual problems. But what needs to be done if you want to integrate a software system (or part thereof) where there are no modules available? Calling out to shell commands won't work to well for complex tasks. You'll find the slides at https://www.jochen.org/vortraege/implementing-salt-modules.pdf We've implemented - as part of a bigger automation effort - some SALT modules to configure our SAP HANA applications for better integration into the automation machinery. I'll present our motivation for implementing execution and state modules, how you can start implementing and testing them. In my experience the function signatures of the modules are the key to useful state modules, so I'll take a look at our modules and discuss the experiences gained in using them. Is the effort worth the gain? My answer is "yes". Some basic programming skills and Python will be helpful for understanding, but not required. We are using SALT to deploy SUSE Systems for production. The included modules work well for usual problems. But what needs to be done if you want to integrate a software system (or part thereof) where there are no modules available? Calling out to shell commands won't work to well for complex tasks. You'll find the slides at https://www.jochen.org/vortraege/implementing-salt-modules.pdf We've implemented - as part of a bigger automation effort - some SALT modules to configure our SAP HANA applications for better integration into the automation machinery. I'll present our motivation for implementing execution and state modules, how you can start implementing and testing them. In my experience the function signatures of the modules are the key to useful state modules, so I'll take a look at our modules and discuss the experiences gained in using them. Is the effort worth the gain? My answer is "yes". Some basic programming skills and Python will be helpful for understanding, but not required. about this event: https://c3voc.de

Rancher can deploy and manage your Kubernetes clusters on AWS EKS and EC2. But what about things like Authentication, Logging, Monitoring or Backup? I will give an overview of AWS services for these four pillars and talk about what’s already possible, which challenges some integrations might have and an outlook what’s planned. Learn more about how the integrations are working under the hood and which technologies and open-sources solutions are involved. Rancher can deploy and manage your Kubernetes clusters on AWS EKS and EC2. But what about things like Authentication, Logging, Monitoring or Backup? I will give an overview of AWS services for these four pillars and talk about what’s already possible, which challenges some integrations might have and an outlook what’s planned. Learn more about how the integrations are working under the hood and which technologies and open-sources solutions are involved. about this event: https://c3voc.de

This talk will cover the development of an openSUSE based external-dns solution that can be used within a k3s environment. The current upstream solution for external-dns is based on Alpine Linux. In order to create containers based on openSUSE, powerdns and external-dns containers were developed and published to registry.opensuse.org. During this session, the different design decisions and hurdles that were overcome will be covered. In addition, the presentation will provide tools, tips, and troubleshooting techniques that were used during the development cycle. This talk will cover the development of an openSUSE based external-dns solution that can be used within a k3s environment. The current upstream solution for external-dns is based on Alpine Linux. In order to create containers based on openSUSE, powerdns and external-dns containers were developed and published to registry.opensuse.org. During this session, the different design decisions and hurdles that were overcome will be covered. In addition, the presentation will provide tools, tips, and troubleshooting techniques that were used during the development cycle. about this event: https://c3voc.de

With SUSE's ALP stirring up discussions how Linux distribution may look like, we decided to try different approach how installer may work. Part of these installer try-outs is **Iguana** - installation initramfs where all heavy lifting is done in containers. Moving installers to the containers and by leveraging container infrastructure, we are trying to solve ever changing requirements or need to have security and other fixes in installer, which was always a bit of challenge for relatively static things like OS installers. With SUSE's ALP stirring up discussions how Linux distribution may look like, we decided to try different approach how installer may work. Part of these installer try-outs is **Iguana** - installation initramfs where all heavy lifting is done in containers. Moving installers to the containers and by leveraging container infrastructure, we are trying to solve ever changing requirements or need to have security and other fixes in installer, which was always a bit of challenge for relatively static things like OS installers. about this event: https://c3voc.de

WASM affords portability when coupled with Content Addressable Tar Files, we can utilize Peer.2 Peer distribution to enhance and reduce the size and vitality of images. This talk explores how the next evolution of containers might take place, and what key technologies are driving solutions in place today. WASM affords portability when coupled with Content Addressable Tar Files, we can utilize Peer.2 Peer distribution to enhance and reduce the size and vitality of images. This talk explores how the next evolution of containers might take place, and what key technologies are driving solutions in place today. about this event: https://c3voc.de

Packaging for a distribution means taking sources from upstream projects, applying fixes and modifications, adding some configuration and then build the result by calling some commands. RPM formalized the process following a "pristine sources" model. The approach is basically to take the unmodified sources as released by upstream and store required changes in the form of patches as well as a build description next to them. Times have changed. The distributed version control system git dominates the free software world. Juggling tarballs and manually applying patches is no longer a natural workflow. Packager life could be much easier if downstream changes could be applied by means of git too, skipping tarballs. This talks presents a way how to apply the pristine source idea to a git based world, without history rewriting in the distro repo. Packaging for a distribution means taking sources from upstream projects, applying fixes and modifications, adding some configuration and then build the result by calling some commands. RPM formalized the process following a "pristine sources" model. The approach is basically to take the unmodified sources as released by upstream and store required changes in the form of patches as well as a build description next to them. Times have changed. The distributed version control system git dominates the free software world. Juggling tarballs and manually applying patches is no longer a natural workflow. Packager life could be much easier if downstream changes could be applied by means of git too, skipping tarballs. This talks presents a way how to apply the pristine source idea to a git based world, without history rewriting in the distro repo. about this event: https://c3voc.de

After some years from first openSUSE image for a mobile phone, i think it is time to let people know about status of project for this topic. In other hand the talk will check features already working and some not fixed, of course at the end there will be a resume about future of the project. This talk will show to everyone wich devices can be considered to be used in a daily drive devices and wich ones are having improvements and will be usable in future. After some years from first openSUSE image for a mobile phone, i think it is time to let people know about status of project for this topic. In other hand the talk will check features already working and some not fixed, of course at the end there will be a resume about future of the project. This talk will show to everyone wich devices can be considered to be used in a daily drive devices and wich ones are having improvements and will be usable in future. about this event: https://c3voc.de

Both the ISO 27001 and ISO 27002 standards have been updated in 2022. What does this mean for open source communities and companies leveraging open source? What are the most significant changes to the standards? The new ISO27001 standard requires companies to identify and meet the needs of interested parties, such as customers and suppliers. That way, organizations can ensure that their information security management system is designed to meet their stakeholders needs. It also requires that organizations include processes for managing information security objectives in their ISMS, so that those objectives can be monitored and evaluated over time. It is essential for organizations to be able to demonstrate that their data-protection and security risk mitigation measures will be maintained and continuously improved. The new ISO27001 standard also makes it clear that changes to an organization's ISMS must be planned, with a specific process for communicating those changes to interested parties. This process should establish how communication should occur (rather than just who should communicate). Organizations now have to control processes, products, or services that are outside of the ISMS (as well as those that are inside of it), which means that they have to take a more holistic approach to managing both internal and outsourced operations. ISO 27002 has been updated, firstly the phrase 'code of practice' has been dropped from the title of the updated ISO 27002 standard. This approach better reflects the set's intended purpose as a reference of information security controls. The 27002 Standard itself is considerably longer than the previous version, and the controls have been reordered and updated. The new controls are identifiable by attribute, which makes it easier to focus on relevant categorical selections, which could reduce the compliance burden or help better integrate information security processes, making the ISMS easier to implement and manage. What is a reasonable for IT vendors and open source communities to update their cybersecurity approach to reflect the new requirements from the new norms? Both the ISO 27001 and ISO 27002 standards have been updated in 2022. What does this mean for open source communities and companies leveraging open source? What are the most significant changes to the standards? The new ISO27001 standard requires companies to identify and meet the needs of interested parties, such as customers and suppliers. That way, organizations can ensure that their information security management system is designed to meet their stakeholders needs. It also requires that organizations include processes for managing information security objectives in their ISMS, so that those objectives can be monitored and evaluated over time. It is essential for organizations to be able to demonstrate that their data-protection and security risk mitigation measures will be maintained and continuously improved. The new ISO27001 standard also makes it clear that changes to an organization's ISMS must be planned, with a specific process for communicating those changes to interested parties. This process should establish how communication should occur (rather than just who should communicate). Organizations now have to control processes, products, or services that are outside of the ISMS (as well as those that are inside of it), which means that they have to take a more holistic approach to managing both internal and outsourced operations. ISO 27002 has been updated, firstly the phrase 'code of practice' has been dropped from the title of the updated ISO 27002 standard. This approach better reflects the set's intended purpose as a reference of information security controls. The 27002 Standard itself is considerably longer than the previous version, and the controls have been reordered and updated. The new controls are identifiable by attribute, which makes it easier to focus on relevant categorical selections, which could reduce the compliance burden or help better integrate information security processes, making the ISMS easier to implement and manage. What is a reasonable for IT vendors and open source communities to update their cybersecurity approach to reflect the new requirements from the new norms? about this event: https://c3voc.de

The famous inventor Zangemann lives in a huge villa high above the city. Adults and children alike love his inventions and are desperate to have them. But then something happens: when Zangemann wants to take another close-up look at his inventions during a walk through the city, a child hits him in the shin with the skateboard. That hurts! Enraged, the inventor makes a momentous decision... The clever girl Ada sees through what is going on. Together with her friends, she forges a plan. This illustrated children's book (licensed under Creative Commons BY-SA) tells the story of the famous inventor Zangemann and the girl Ada, a curious tinkerer. Ada begins to experiment with hardware and software, and in the process realizes how crucial it is for her and others to control technology. Ada & Zangemann will inspire children's interest in tinkering and encourages shaping technology. > "A rousing tale of self-reliance, community, and standing up to bullies." —Cory Doctorow, Sci-Fi Author > "Ada & Zangemann proves that the argument for software and hardware freedom is simple: We should be able to do what we want with our stuff. . . . Electronics freedom means more learning and less waste, as Ada shows. Kids and adults alike will be entertained by this book, charmed by its illustrations, and inspired by Ada’s engineering spirit and impassioned activism." —Elizabeth Chamberlain, Director of Sustainability, iFixit > "What a fun read! I recognize myself in Ada at many moments." —Isabela Fernandes, Executive Director, The Tor project > "Even as a non-child, I was captivated by the story from the first page to the last. Kudos to the author for packaging difficult topics such as monopolies, lobbyism, digital divide, software freedom, digital autonomy, IoT, consumer control, e-waste and much more in a child-friendly form in an easily understandable and exciting storyline." —Jörg Luther, chief editor of the German Linux-Magazin, LinuxUser [Download the slides of the talk here](https://download.fsfe.org/presentations/20230526-mk-opensuse-ada-zangemann-reading.en.pdf) and you generic slides for doing your own readings with the book are available [in the FSFE's book repository](https://git.fsfe.org/FSFE/ada-zangemann). The famous inventor Zangemann lives in a huge villa high above the city. Adults and children alike love his inventions and are desperate to have them. But then something happens: when Zangemann wants to take another close-up look at his inventions during a walk through the city, a child hits him in the shin with the skateboard. That hurts! Enraged, the inventor makes a momentous decision... The clever girl Ada sees through what is going on. Together with her friends, she forges a plan. This illustrated children's book (licensed under Creative Commons BY-SA) tells the story of the famous inventor Zangemann and the girl Ada, a curious tinkerer. Ada begins to experiment with hardware and software, and in the process realizes how crucial it is for her and others to control technology. Ada & Zangemann will inspire children's interest in tinkering and encourages shaping technology. > "A rousing tale of self-reliance, community, and standing up to bullies." —Cory Doctorow, Sci-Fi Author > "Ada & Zangemann proves that the argument for software and hardware freedom is simple: We should be able to do what we want with our stuff. . . . Electronics freedom means more learning and less waste, as Ada shows. Kids and adults alike will be entertained by this book, charmed by its illustrations, and inspired by Ada’s engineering spirit and impassioned activism." —Elizabeth Chamberlain, Director of Sustainability, iFixit > "What a fun read! I recognize myself in Ada at many moments." —Isabela Fernandes, Executive Director, The Tor project > "Even as a non-child, I was captivated by the story from the first page to the last. Kudos to the author for packaging difficult topics such as monopolies, lobbyism, digital divide, software freedom, digital autonomy, IoT, consumer control, e-waste and much more in a child-friendly form in an easily understandable and exciting storyline." —Jörg Luther, chief editor of the German Linux-Magazin, LinuxUser [Download the slides of the talk here](https://download.fsfe.org/presentations/20230526-mk-opensuse-ada-zangemann-reading.en.pdf) and you generic slides for doing your own readings with the book are available [in the FSFE's book repository](https://git.fsfe.org/FSFE/ada-zangemann). about this event: https://c3voc.de

Ask your questions about the new Adaptable Linux Platform. This will be a discussion format with ALP Architects. Get all the answers about the next generation product line in this open format discussion. Ask your questions about the new Adaptable Linux Platform. This will be a discussion format with ALP Architects. Get all the answers about the next generation product line in this open format discussion. about this event: https://c3voc.de