Chaos Computer Club - archive feed

The speaker works for a small company in the UK who have developed a VTVL (Vertical Take-off, Vertical Landing) rocket, also known as a hopper or lander. This started as a student / hobby project and is now receiving funding from the European Space Agency (ESA.) There are lots of interesting technical problems involved in making a VTVL rocket work. You need to steer the rocket engine and control its thrust based on data from a variety of sensors. This involves mechanical, electronics and coding challenges. When fully developed, the test vehicle we've developed will be used to test software and hardware that enable robots to land safely on other planets such as Mars. The talk will start with an introduction to rocket engines and a simple explanation of the vehicle's dynamics then cover the development of our VTVL rocket from hobby project to successful flying test-bed. It will include video footage of recent test flights where the rocket takes off and hovers on a tethered test rig. about this event: https://c3voc.de

PAMAL_Group is a European artistic group, composed of artists, media theorists, curators-restorers and engineers. Their artwork "3615 Love" will be installed at EMF 2022. PAMAL_Group creates its own works from digital artworks that have disappeared or been severely damaged due to the obsolescence of computer software and hardware. Its work seeks to reveal the vulnerability of an art that is highly dependent on industrial logic. All the artworks that the collective reconstructs, as close as possible to the original materialities, sometimes in a deficient way, are treated as archives. The artwork "3615 Love" is based on the reconstruction of telematic materialities (videotex, Minitel network, etc.) and the archive of works by Jacques-Elie Chabert and Camille Philibert (L'Objet perdu, 1985) and Eduardo Kac (Videotext Poems, 1985-1986). The installation "3615 Love" shows how fragile and vulnerable our digital environment - and a fortiori its artistic productions - is. about this event: https://c3voc.de

YaST, the flagship installer and configuration tool of openSUSE is in constant development. Just as its unattended companion AutoYaST. Although the YaST Team at SUSE tries to communicate progress as often as possible in the YaST Blog, it has been almost two years since we presented the "Top 25 New Features in (Auto)YaST" at openSUSE Conference 2020. So it's time for another live update! We will recap the main changes and new features that are already integrated into openSUSE Tumbleweed and that will be included at openSUSE Leap 15.4, to be released just a couple of days after the talk. We will also take a look to some ideas for future development... and we really need the feedback of the whole openSUSE community for that. So please join us and speak up! YaST, the flagship installer and configuration tool of openSUSE is in constant development. Just as its unattended companion AutoYaST. Although the YaST Team at SUSE tries to communicate progress as often as possible in the YaST Blog, it has been almost two years since we presented the "Top 25 New Features in (Auto)YaST" at openSUSE Conference 2020. So it's time for another live update! We will recap the main changes and new features that are already integrated into openSUSE Tumbleweed and that will be included at openSUSE Leap 15.4, to be released just a couple of days after the talk. We will also take a look to some ideas for future development... and we really need the feedback of the whole openSUSE community for that. So please join us and speak up! about this event: https://c3voc.de

It's no news or secret that containers are good at providing multiple and different testing environments, or at offering a way of deploying apps and services that are completely decoupled from the host OS. E.g., spin up a distro X container, check if code compiles there (and dispose of it). How about the opposite? I.e., having one (or more!) stateful and persistent environment(s), tightly coupled with the host and sharing as much information and configuration as possible with it. Why? Well for running that one app, which is only available for another distro, with just a click on a desktop launcher icon. Or for doing all kind of experiments, inside our development environment, without risking the stability and the consistency of the system. Well, yes, containers can do these things too. And in openSUSE, we have both toolbox and distrobox, that can make these examples, just reality! In this talk, we'll explain what they are and how to use them for spawning development and application environments, based either on the same distro you have on the host or on different ones, and inside of which you still have all your file. A working space that, despite being containerized, you can access seamlessly from within GNOME Builder or open new terminals directly inside of it and create launcher icons for apps installed in there. We'll offer (more) examples and show how this can be very useful, both on immutable (like MicroOS) and on "traditional" (like Tumbleweed) systems. It's no news or secret that containers are good at providing multiple and different testing environments, or at offering a way of deploying apps and services that are completely decoupled from the host OS. E.g., spin up a distro X container, check if code compiles there (and dispose of it). How about the opposite? I.e., having one (or more!) stateful and persistent environment(s), tightly coupled with the host and sharing as much information and configuration as possible with it. Why? Well for running that one app, which is only available for another distro, with just a click on a desktop launcher icon. Or for doing all kind of experiments, inside our development environment, without risking the stability and the consistency of the system. Well, yes, containers can do these things too. And in openSUSE, we have both toolbox and distrobox, that can make these examples, just reality! In this talk, we'll explain what they are and how to use them for spawning development and application environments, based either on the same distro you have on the host or on different ones, and inside of which you still have all your file. A working space that, despite being containerized, you can access seamlessly from within GNOME Builder or open new terminals directly inside of it and create launcher icons for apps installed in there. We'll offer (more) examples and show how this can be very useful, both on immutable (like MicroOS) and on "traditional" (like Tumbleweed) systems. about this event: https://c3voc.de

We've all found ourself doomscrolling, and fighting against social network's barrage of extra things in our newsfeed and notifications to keep us there for longer. It's not good use of time, energy and mental bandwith, and hell in my case the habitual refreshing has started giving me RSI. I'll go through my three steps to stop Doomscrolling and get out of the social media refresh loop (or at least try to). about this event: https://c3voc.de

The largest and the highest energy scientific device - the Large Hadron Collider (LHC) is currently in operation at CERN. This machine is unique in many respects: - It is the most powerful microscope, which can probe the distance one million times smaller than the size of the proton - It can reproduce conditions of the hot Early Universe with the temperature billion times higher than in the core of the sun, corresponding to a picosecond after the Big Bang This uniqueness gives the LHC opportunity to resolve the biggest puzzles of the Universe: - to find the origin of Matter-Antimatter asymmetry – the origin of planets and starts - to Shed a light on the origin of Dark Matter and Dark Energy, 95% of which the Universe is made of (stars and planets contribute only 5% to it !) - to give us the answer on what is the ultimate theory which drives this Universe – at micro and macro scales. In the presentation I will explain the exciting details of the Large Hadron Collider and how it helps to solve the most challenging problems of particle physics and cosmology – from micro to macro scales. https://docs.google.com/presentation/d/1YiUERbdFC7pUVuayv8Swxslz5TvL8X-yFvkLq_1cvNs/edit?usp=sharing about this event: https://c3voc.de

AutoYaST is the main method for installing openSUSE Linux in enterprise environments. Although it is usual for AutoYaST to get new features and fixes with every minor release, openSUSE Leap 15.3 was special in that regard. Thanks to the "Modernizing AutoYaST" initiative, we introduced relevant features like ERB templates, better validation tools, etc. However, we have found that many of these features remain unknown to our users, and the openSUSE Conference offers an excellent chance to present them. AutoYaST is the main method for installing openSUSE Linux in enterprise environments. Although it is usual for AutoYaST to get new features and fixes with every minor release, openSUSE Leap 15.3 was special in that regard. Thanks to the "Modernizing AutoYaST" initiative, we introduced relevant features like ERB templates, better validation tools, etc. However, we have found that many of these features remain unknown to our users, and the openSUSE Conference offers an excellent chance to present them. about this event: https://c3voc.de

We take a scenic tour through the origins of the UK train ticket, from the original BR specification in the 1980s through to modern replacements like mTickets, eTickets and ITSO. This is just a detour though, and we'll focus on the 'orange ticket' (RSP 9399/9599) - which continues to be a stalwart of the UK rail network. Surely they can't be that secure? After all, anyone can encode a magstripe - right? We'll take a look through the data encoded on these tickets, what interesting things you can do with them and maybe (assuming I've got it working by then) we'll be able to read and write our own! about this event: https://c3voc.de

My experiences over the last 2-4 months learning to update packages in openSUSE. Starting around the middle of March 2022, I began learning to update packages with OBS. This lightening talk with highlight my experiences since then learning to package. My experiences over the last 2-4 months learning to update packages in openSUSE. Starting around the middle of March 2022, I began learning to update packages with OBS. This lightening talk with highlight my experiences since then learning to package. about this event: https://c3voc.de

Ask your questions about the new Adaptable Linux Platform. This will be a discussion format with the ALP steering committee. 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 the ALP steering committee. Get all the answers about the next generation product line in this open format discussion. about this event: https://c3voc.de

Last year, I ported [oreboot](https://github.com/oreboot) to the Allwinner D1 SoC that is found on the Nezha SBC and many other boards now. For a boot loader environment, I chose to embed [LinuxBoot](https://linuxboot.org), and then partitioned an SD card with two root filesystems for testing: OpenWrt, which is small and just ran right away, and openSUSE, which required some extra effort. I was happy to see a new D1 board advertised with openSUSE support, though the process of getting there was tedious enough that I wanted to find an improvement to the workflow. In this talk, I will recap how I modified the openSUSE RISC-V root filesystem, moving an SD card back and forth, and showcase a faster approach instead by leveraging the [`cpu`](https://github.com/u-root/cpu) command that lets us do that iteration over the network. Eventually, we will see how that can be leveraged to continuously test Tumbleweed on real hardware through OpenQA and a corresponding setup, which can also be applied to other hardware, such as ARM. Last year, I ported [oreboot](https://github.com/oreboot) to the Allwinner D1 SoC that is found on the Nezha SBC and many other boards now. For a boot loader environment, I chose to embed [LinuxBoot](https://linuxboot.org), and then partitioned an SD card with two root filesystems for testing: OpenWrt, which is small and just ran right away, and openSUSE, which required some extra effort. I was happy to see a new D1 board advertised with openSUSE support, though the process of getting there was tedious enough that I wanted to find an improvement to the workflow. In this talk, I will recap how I modified the openSUSE RISC-V root filesystem, moving an SD card back and forth, and showcase a faster approach instead by leveraging the [`cpu`](https://github.com/u-root/cpu) command that lets us do that iteration over the network. Eventually, we will see how that can be leveraged to continuously test Tumbleweed on real hardware through OpenQA and a corresponding setup, which can also be applied to other hardware, such as ARM. about this event: https://c3voc.de

The development model for the classic release distribution of openSUSE - Leap - has changed several times. Currently it shares the binaries with SUSE SLE. This has advantages, but as well limitations. The talk explains how the development model has evolved and its current pitfalls. In the second part we will introduce the Adaptable Linux Platform (ALP) and discuss the current state of development The development model for the classic release distribution of openSUSE - Leap - has changed several times. Currently it shares the binaries with SUSE SLE. This has advantages, but as well limitations. The talk explains how the development model has evolved and its current pitfalls. In the second part we will introduce the Adaptable Linux Platform (ALP) and discuss the current state of development about this event: https://c3voc.de

centre is a simple Go program (github.com/https://github.com/Harvey-OS/go/tree/main/cmd/centre), which runs as a daemon or interactive program and lets you manage all your IoT devices with one file -- formatted like /etc/hosts. centre was originally written for Plan 9 networks, but is becoming widely used for many other Oses. Like many of us, I have a house full of IoT and server systems, some running Plan 9, some Linux, and all of which need DHCP, TFTP, HTTP, and 9P boot services. Over the years, I've had my fun with various DHCP daemons, TFTP and HTTP boot servers, and 9p servers for Plan 9. All of these needed configuration files in all kinds of formats, and all had lots of ways to fail with each new upgrade. centre removes these headaches. With just one program, one directory, and one configuration file, all the services you need are managed by the centre. In this talk, I'll go over what it is, how to set it up, and how it works. centre is a simple Go program (github.com/https://github.com/Harvey-OS/go/tree/main/cmd/centre), which runs as a daemon or interactive program and lets you manage all your IoT devices with one file -- formatted like /etc/hosts. centre was originally written for Plan 9 networks, but is becoming widely used for many other Oses. Like many of us, I have a house full of IoT and server systems, some running Plan 9, some Linux, and all of which need DHCP, TFTP, HTTP, and 9P boot services. Over the years, I've had my fun with various DHCP daemons, TFTP and HTTP boot servers, and 9p servers for Plan 9. All of these needed configuration files in all kinds of formats, and all had lots of ways to fail with each new upgrade. centre removes these headaches. With just one program, one directory, and one configuration file, all the services you need are managed by the centre. In this talk, I'll go over what it is, how to set it up, and how it works. about this event: https://c3voc.de

Spring Forward, Fall Back... but why? Take a trip from Railway Time to the Olson database, as we explore the strange history of Time Zones and Daylight Saving Time. about this event: https://c3voc.de

DNS is at the heart of the network. Without it, we are hopelessly lost. We can't even google for it. It allows us humans to map the network into the human domain and vice-versa. Yet we ignore it as unimportant part of network security fabric and allow individual unnamed corporation to control over 20% the internet lookups, because they are not evil. This presentation should serve as a quick survey of DNS technologies from basic overview of how DNS works, to DoT, DoH, and DNScrypt. Finally we cover DNSSEC and reasons we should stop ignoring it if we want a trustworthy and resilient infrastructure. Finally we will cover why running your own DNS server should be the first thing you do to secure your own networks. Fun Fact: pdns-recursor in openSUSE is DNSSEC validating by default for half a decade already DNS is at the heart of the network. Without it, we are hopelessly lost. We can't even google for it. It allows us humans to map the network into the human domain and vice-versa. Yet we ignore it as unimportant part of network security fabric and allow individual unnamed corporation to control over 20% the internet lookups, because they are not evil. This presentation should serve as a quick survey of DNS technologies from basic overview of how DNS works, to DoT, DoH, and DNScrypt. Finally we cover DNSSEC and reasons we should stop ignoring it if we want a trustworthy and resilient infrastructure. Finally we will cover why running your own DNS server should be the first thing you do to secure your own networks. Fun Fact: pdns-recursor in openSUSE is DNSSEC validating by default for half a decade already about this event: https://c3voc.de

You're shopping for new hardware, but you're not sure if it will be supported by openSUSE? This talk explains some basics on how hardware support works and what ways you have to find out if your hardware is supported or not. After 17 years of Linux hardware compatibility testing and hardware certification I can tell some good advice. You're shopping for new hardware, but you're not sure if it will be supported by openSUSE? This talk explains some basics on how hardware support works and what ways you have to find out if your hardware is supported or not. After 17 years of Linux hardware compatibility testing and hardware certification I can tell some good advice. about this event: https://c3voc.de

The ceremony in which we open the event about this event: https://c3voc.de

<p>Seit Jahren fliehen Menschen aus Krisen- und Kriegsregionen über die sogenannte Balkanroute, auf der Suche nach einem sicheren Ort zum Leben. People on the Move stecken, im bosnischen Grenzkanton Una-Sana, in einer „Sackgasse“, weil die kroatische Polizei systematisch gewaltvolle Pushbacks, also illegale Rückführungen aus Kroatien nach Bosnien, durchführt.</p><p>Diese rechtswidrige, unmenschliche Praxis wird von der EU mitfinanziert. In Bosnien und Herzegowina ist die Situation für die Fliehenden katastrophal: unter menschenunwürdigen Bedingungen leben sie in Zelten und Ruinen.</p><p>Seit dem Februar 2022 fliehen circa 5 Millionen Menschen aufgrund des Angriffskriegs in der Ukraine und viele konnten innerhalb kürzester Zeit sichere Orte in der EU finden. Dieses Verantwortungsbewusstsein und die gelebte Solidarität für ukrainische Menschen auf der Flucht, zeigt was möglich ist, wenn der politische Wille zum Handeln vorhanden ist: sichere Fluchtwege und offene Grenzen sind umsetzbar!</p><p>Wie kann dieser politische Willen genutzt und ausweitet werden? Wie kann Aufmerksamkeit verteilt werden? Und welche Rolle spielen Vereine die People on the Move unterstützen dabei?</p><p>Im Rahmen der monatlich stattfindenden Veranstaltung "Debate! Humanitarian Aid" von Cadus e.V., berichtet <a href="https://blindspots.support/" rel="noopener" target="_blank">Blindspots</a> von der aktuellen Lage im bosnisch-kroatischen und slowakisch-ukrainischen Grenzgebiet und zeigt dabei Lebensrealitäten von Menschen vor Ort auf. Zudem wird die Arbeit von Blindspots vorgestellt – einem Verein, der People on the Move unter dem Motto „SolidarityWithoutBorders“ unterstützt.</p> about this event: https://cadus.org/debate

At SUSE, and openSUSE we have short feedback loops to ensure compliance with a range of certifications, but our tools can have real world impact beyond the physical barriers, I will talk about how openQA can support operations in Healthcare, Manufacturing, Automotive, Edge, Transportation, and Elections. At SUSE, and openSUSE we have short feedback loops to ensure compliance with a range of certifications, but our tools can have real world impact beyond the physical barriers, I will talk about how openQA can support operations in Healthcare, Manufacturing, Automotive, Edge, Transportation, and Elections. about this event: https://c3voc.de

In this talk I'm gonna talk about how we use self hosted and open source solutions at school. In this talk I'm gonna talk about how we use self hosted and open source solutions at school. about this event: https://c3voc.de

As the world moves to using machine learning more and more, a question arises of how to prevent cyber criminals from attacking systems using ML frameworks. In this talk, we will cover why machine learning needs security practices and how we develop TensorFlow to be secure. We will discuss topics such as fuzzing and code transformations for secure software development with a focus on how these are applied within TensorFlow ecosystem. As the world moves to using machine learning more and more, a question arises of how to prevent cyber criminals from attacking systems using ML frameworks. In this talk, we will cover why machine learning needs security practices and how we develop TensorFlow to be secure. We will discuss topics such as fuzzing and code transformations for secure software development with a focus on how these are applied within TensorFlow ecosystem. about this event: https://c3voc.de

warewulf4 is a rewrite of the well known warewulf cluster management tool in golang. With this new iteration its possible to leverage the possibilities which emerged with broad use of containers. The origins of warewulf4 is the hpcng community which is/was also behind projects like Apptainer (former known as Singularity), Centos and Rocky linux. A basic setup of a HPC cluster and the key concept of the configuration mechanism of warewulf4 are covered in this talk. warewulf4 is a rewrite of the well known warewulf cluster management tool in golang. With this new iteration its possible to leverage the possibilities which emerged with broad use of containers. The origins of warewulf4 is the hpcng community which is/was also behind projects like Apptainer (former known as Singularity), Centos and Rocky linux. A basic setup of a HPC cluster and the key concept of the configuration mechanism of warewulf4 are covered in this talk. about this event: https://c3voc.de

This talk will introduce the SUSE Product Security team, who handles the software security processes for openSUSE and also SUSE Linux Enterprise. The SUSE Product Security work is split into "reactive" and "proactive" areas and engineering groups these days. Reactive work refering to what is traditionally known as "security incident response", while proactive refers to security audits, design reviews and related areas of secure software development. The talk will focus on the reactive side, giving statistics, and talk about some highlights from the last year. Also bringing a small overview over how closing the leap gap changes affects the openSUSE Maintenance process. This talk will introduce the SUSE Product Security team, who handles the software security processes for openSUSE and also SUSE Linux Enterprise. The SUSE Product Security work is split into "reactive" and "proactive" areas and engineering groups these days. Reactive work refering to what is traditionally known as "security incident response", while proactive refers to security audits, design reviews and related areas of secure software development. The talk will focus on the reactive side, giving statistics, and talk about some highlights from the last year. Also bringing a small overview over how closing the leap gap changes affects the openSUSE Maintenance process. about this event: https://c3voc.de

Recently MicroOS can be installed with remote attestation, using the TPM as a root of trust and Keylime as a service to report and verify the status of our systems. In this talk we will see what is a TPM, how Keylime can be installed in MicroOS and used to monitor the health of our system in production and what to do when we detect a compromised system. Recently MicroOS can be installed with remote attestation, using the TPM as a root of trust and Keylime as a service to report and verify the status of our systems. In this talk we will see what is a TPM, how Keylime can be installed in MicroOS and used to monitor the health of our system in production and what to do when we detect a compromised system. about this event: https://c3voc.de

The SUSE QE Tools Team - Who we are and what we are doing. This talk will give an overview of who is the SUSE QE Tools team, what is in our responsibility, what we did in the past time and what we do. The products that we care about will be presented and the workflows of the team will be shown. Opportunities for contributions will be discussed. https://v.gd/okurz_osc22 The SUSE QE Tools Team - Who we are and what we are doing. This talk will give an overview of who is the SUSE QE Tools team, what is in our responsibility, what we did in the past time and what we do. The products that we care about will be presented and the workflows of the team will be shown. Opportunities for contributions will be discussed. https://v.gd/okurz_osc22 about this event: https://c3voc.de

The SLE Base Container Images (BCI) want to create a flexible developer experience that provides, integrates with, and supports language native tools and workflows by offering a self-contained environment targeting a specific version of any given programming language ecosystem to facilitate software development, testing and deployment.​ These images are meant to run on any Linux and K8s distributions, are freely redistributable and come with a pre-configured repository offering the same enterprise grade packages shipped by SUSE flagship product SUSE Linux Enterprise Server. The freely available repository offers a lighter set of packages carefully cherry-picked from the official SLES repositories, however it is possible to push an already purchased SLES subscription to these images hence having access to the full universe of packages available. The SLE Base Container Images (BCI) want to create a flexible developer experience that provides, integrates with, and supports language native tools and workflows by offering a self-contained environment targeting a specific version of any given programming language ecosystem to facilitate software development, testing and deployment.​ These images are meant to run on any Linux and K8s distributions, are freely redistributable and come with a pre-configured repository offering the same enterprise grade packages shipped by SUSE flagship product SUSE Linux Enterprise Server. The freely available repository offers a lighter set of packages carefully cherry-picked from the official SLES repositories, however it is possible to push an already purchased SLES subscription to these images hence having access to the full universe of packages available. about this event: https://c3voc.de