https://media.ccc.de/c/osc22 This feed contains all events from osc22 as mp4 see video outro Thu, 23 Jan 2025 18:42:42 -0000 https://static.media.ccc.de/media/events/osc/2022/oSC22icon.png https://media.ccc.de/c/osc22 https://media.ccc.de/v/3686-authenticating-open-source-cloud-applications-with-ldap It is very common for businesses with small teams to use cloud services to synchronise their work, stay in touch etc. All of these can also be achieved using open source software. However, making the different open source applications to authenticate through a single mechanism is somewhat challenging. In this presentation, I will cover the use of LDAP to authenticate cloud services like Nextcloud and Rocket.Chat. I'll cover 389 Directory Server to provide the LDAP service. It is very common for businesses with small teams to use cloud services to synchronise their work, stay in touch etc. All of these can also be achieved using open source software. However, making the different open source applications to authenticate through a single mechanism is somewhat challenging. In this presentation, I will cover the use of LDAP to authenticate cloud services like Nextcloud and Rocket.Chat. I'll cover 389 Directory Server to provide the LDAP service. about this event: https://c3voc.de Sat, 04 Jun 2022 16:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3686-eng-Authenticating_open_source_cloud_applications_with_LDAP_sd.mp4?1687411609 Jvyqi8y7VYb23UjLQEQ8IA 2022-06-04T16:30:00+02:00 Ish Sookun No osc22, 3686, 2022, Cloud and Containers Featuring Nextcloud & Rocket.Chat It is very common for businesses with small teams to use cloud services to synchronise their work, stay in touch etc. All of these can also be achieved using open source software. However, making the different open source applications to authenticate through a single mechanism is somewhat challenging. In this presentation, I will cover the use of LDAP to authenticate cloud services like Nextcloud and Rocket.Chat. I'll cover 389 Directory Server to provide the LDAP service. It is very common for businesses with small teams to use cloud services to synchronise their work, stay in touch etc. All of these can also be achieved using open source software. However, making the different open source applications to authenticate through a single mechanism is somewhat challenging. In this presentation, I will cover the use of LDAP to authenticate cloud services like Nextcloud and Rocket.Chat. I'll cover 389 Directory Server to provide the LDAP service. about this event: https://c3voc.de 00:21:19 https://media.ccc.de/v/3902-alp-community-wg-recommended-ways-to-communicate-with-the-community This talk focuses on effective communication with the openSUSE community. Many workgroups have formed around the new Adaptable Linux Platform. However, not all of them are reporting the public yet. [ALP Community Work Group ](https://en.opensuse.org/openSUSE:ALP/Workgroups/Community)would like to encourage workgroup drivers to increase transparency by sharing our recommendations on how to communicate with the openSUSE community. This talk focuses on effective communication with the openSUSE community. Many workgroups have formed around the new Adaptable Linux Platform. However, not all of them are reporting the public yet. [ALP Community Work Group ](https://en.opensuse.org/openSUSE:ALP/Workgroups/Community)would like to encourage workgroup drivers to increase transparency by sharing our recommendations on how to communicate with the openSUSE community. about this event: https://c3voc.de Sat, 04 Jun 2022 15:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3902-eng-ALP_Community_WG_Recommended_ways_to_communicate_with_the_community_sd.mp4?1687407346 Lm8IXtKCjRogsZzA9UAsEw 2022-06-04T15:30:00+02:00 Lubos Kocman No osc22, 3902, 2022, openSUSE This talk focuses on effective communication with the openSUSE community. Many workgroups have formed around the new Adaptable Linux Platform. However, not all of them are reporting the public yet. [ALP Community Work Group ](https://en.opensuse.org/openSUSE:ALP/Workgroups/Community)would like to encourage workgroup drivers to increase transparency by sharing our recommendations on how to communicate with the openSUSE community. This talk focuses on effective communication with the openSUSE community. Many workgroups have formed around the new Adaptable Linux Platform. However, not all of them are reporting the public yet. [ALP Community Work Group ](https://en.opensuse.org/openSUSE:ALP/Workgroups/Community)would like to encourage workgroup drivers to increase transparency by sharing our recommendations on how to communicate with the openSUSE community. about this event: https://c3voc.de 00:41:15 https://media.ccc.de/v/3713-org-mode-manage-your-life-in-plain-text Org mode is an extension to the Emacs text editor. The talk will introduce a trusted system to manage your daily life and keep track of all the stuff that matters to you. The mein difference to other personal productivity apps is: - **You** have control over your files. - Files are in plain text, you can even read them without org mode. - The application is Open Source, so no risk that is discontinued because the business plan didnt work. - The user can customize it for his own needs and is not forced to adapt to the needs of a tool. **About me:** Software Engineer, 25+ years on Linux, using Org mode daily for at least 12 years now. Org mode is an extension to the Emacs text editor. The talk will introduce a trusted system to manage your daily life and keep track of all the stuff that matters to you. The mein difference to other personal productivity apps is: - **You** have control over your files. - Files are in plain text, you can even read them without org mode. - The application is Open Source, so no risk that is discontinued because the business plan didnt work. - The user can customize it for his own needs and is not forced to adapt to the needs of a tool. **About me:** Software Engineer, 25+ years on Linux, using Org mode daily for at least 12 years now. about this event: https://c3voc.de Sat, 04 Jun 2022 15:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3713-eng-Org_mode_Manage_your_life_in_plain_text_sd.mp4?1687401066 l1FCqp9C8ztQgYKpgXF8yg 2022-06-04T15:30:00+02:00 rainerkoenig No osc22, 3713, 2022, Open Source Use Open Source to make your life easier Org mode is an extension to the Emacs text editor. The talk will introduce a trusted system to manage your daily life and keep track of all the stuff that matters to you. The mein difference to other personal productivity apps is: - **You** have control over your files. - Files are in plain text, you can even read them without org mode. - The application is Open Source, so no risk that is discontinued because the business plan didnt work. - The user can customize it for his own needs and is not forced to adapt to the needs of a tool. **About me:** Software Engineer, 25+ years on Linux, using Org mode daily for at least 12 years now. Org mode is an extension to the Emacs text editor. The talk will introduce a trusted system to manage your daily life and keep track of all the stuff that matters to you. The mein difference to other personal productivity apps is: - **You** have control over your files. - Files are in plain text, you can even read them without org mode. - The application is Open Source, so no risk that is discontinued because the business plan didnt work. - The user can customize it for his own needs and is not forced to adapt to the needs of a tool. **About me:** Software Engineer, 25+ years on Linux, using Org mode daily for at least 12 years now. about this event: https://c3voc.de 00:43:41 https://media.ccc.de/v/3908-simpledrm-a-kernel-fbdev-replacement simpledrm is a fbdev replacement implemented in the DRM kernel subsystem. It allows for smoother handover from the early boot phase to when a "real" DRM driver is loaded. In addition it allows for Wayland support on simple display adapters that do not have their own DRM driver. It has already been mainlined for a while but is not in active use by major linux distributions. In this talk I will briefly introduce you to the project and show you how you can test it on your machines. I have recently learned about this effort and started looking at DRM. This talk is held by a kernel newbie. simpledrm is a fbdev replacement implemented in the DRM kernel subsystem. It allows for smoother handover from the early boot phase to when a "real" DRM driver is loaded. In addition it allows for Wayland support on simple display adapters that do not have their own DRM driver. It has already been mainlined for a while but is not in active use by major linux distributions. In this talk I will briefly introduce you to the project and show you how you can test it on your machines. I have recently learned about this effort and started looking at DRM. This talk is held by a kernel newbie. about this event: https://c3voc.de Sat, 04 Jun 2022 14:10:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3908-eng-simpledrm_-_a_kernel_fbdev_replacement_sd.mp4?1687400125 NlTipzjKUIaVWY8VWoyxVg 2022-06-04T14:10:00+02:00 tschmitz No osc22, 3908, 2022, Open Source simpledrm is a fbdev replacement implemented in the DRM kernel subsystem. It allows for smoother handover from the early boot phase to when a "real" DRM driver is loaded. In addition it allows for Wayland support on simple display adapters that do not have their own DRM driver. It has already been mainlined for a while but is not in active use by major linux distributions. In this talk I will briefly introduce you to the project and show you how you can test it on your machines. I have recently learned about this effort and started looking at DRM. This talk is held by a kernel newbie. simpledrm is a fbdev replacement implemented in the DRM kernel subsystem. It allows for smoother handover from the early boot phase to when a "real" DRM driver is loaded. In addition it allows for Wayland support on simple display adapters that do not have their own DRM driver. It has already been mainlined for a while but is not in active use by major linux distributions. In this talk I will briefly introduce you to the project and show you how you can test it on your machines. I have recently learned about this effort and started looking at DRM. This talk is held by a kernel newbie. about this event: https://c3voc.de 00:14:42 https://media.ccc.de/v/3776-rad-cybersecurity-medical-grade-regulatory-compliance-and-open-source-go-hand-in-hand Business processes evolve continuously, customer expectations and requirements change even faster. Process management and workflow support systems have a tendency to grow organically into fearsomely complex monolithic beasts while piling up technical debt in the process. Data migrations come at high cost, changing systems almost always require data to be converted into the new systems particular data model, which makes doing data migration verification both complex as well as costly. Using the open source/free software SQL database engine PostgreSQL, one of the leading Relational Database Management Systems, and in recent years the most popular database engine used in startups and scaleups, takes away the concern of future accessibility and integrity of the data itself. A middleware layer/REST API built with Symfony framework and a ReactJS based frontend ensure a fully responsive modern UX. Furthermore we use GitLab and Ansible for project management and automating our CI/CD environment. At OpenNovations we’ve created a solution called Aranei built with standard open source tools which generates a state of the art, open web standards based, user interface on top of any existing SQL data structure. Keep the same schema/structure between source system and archiving solution, or to use the notion of a controlled copy, is a much less cumbersome approach, as a one on one data verification can be performed. Not just the UI components themselves are generated by the metadata app modeling engine, also automated test scripts and a data dictionary are generated as part of the data verification process. Business processes evolve continuously, customer expectations and requirements change even faster. Process management and workflow support systems have a tendency to grow organically into fearsomely complex monolithic beasts while piling up technical debt in the process. Data migrations come at high cost, changing systems almost always require data to be converted into the new systems particular data model, which makes doing data migration verification both complex as well as costly. Using the open source/free software SQL database engine PostgreSQL, one of the leading Relational Database Management Systems, and in recent years the most popular database engine used in startups and scaleups, takes away the concern of future accessibility and integrity of the data itself. A middleware layer/REST API built with Symfony framework and a ReactJS based frontend ensure a fully responsive modern UX. Furthermore we use GitLab and Ansible for project management and automating our CI/CD environment. At OpenNovations we’ve created a solution called Aranei built with standard open source tools which generates a state of the art, open web standards based, user interface on top of any existing SQL data structure. Keep the same schema/structure between source system and archiving solution, or to use the notion of a controlled copy, is a much less cumbersome approach, as a one on one data verification can be performed. Not just the UI components themselves are generated by the metadata app modeling engine, also automated test scripts and a data dictionary are generated as part of the data verification process. about this event: https://c3voc.de Sat, 04 Jun 2022 13:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3776-eng-RAD_cybersecurity_medical_grade_regulatory_compliance_and_open_source_go_hand_in_hand_sd.mp4?1687396864 jBOgz9Lll4CH6GlDDjCzwA 2022-06-04T13:00:00+02:00 Hans de Raad No osc22, 3776, 2022, Open Source Business processes evolve continuously, customer expectations and requirements change even faster. Process management and workflow support systems have a tendency to grow organically into fearsomely complex monolithic beasts while piling up technical debt in the process. Data migrations come at high cost, changing systems almost always require data to be converted into the new systems particular data model, which makes doing data migration verification both complex as well as costly. Using the open source/free software SQL database engine PostgreSQL, one of the leading Relational Database Management Systems, and in recent years the most popular database engine used in startups and scaleups, takes away the concern of future accessibility and integrity of the data itself. A middleware layer/REST API built with Symfony framework and a ReactJS based frontend ensure a fully responsive modern UX. Furthermore we use GitLab and Ansible for project management and automating our CI/CD environment. At OpenNovations we’ve created a solution called Aranei built with standard open source tools which generates a state of the art, open web standards based, user interface on top of any existing SQL data structure. Keep the same schema/structure between source system and archiving solution, or to use the notion of a controlled copy, is a much less cumbersome approach, as a one on one data verification can be performed. Not just the UI components themselves are generated by the metadata app modeling engine, also automated test scripts and a data dictionary are generated as part of the data verification process. Business processes evolve continuously, customer expectations and requirements change even faster. Process management and workflow support systems have a tendency to grow organically into fearsomely complex monolithic beasts while piling up technical debt in the process. Data migrations come at high cost, changing systems almost always require data to be converted into the new systems particular data model, which makes doing data migration verification both complex as well as costly. Using the open source/free software SQL database engine PostgreSQL, one of the leading Relational Database Management Systems, and in recent years the most popular database engine used in startups and scaleups, takes away the concern of future accessibility and integrity of the data itself. A middleware layer/REST API built with Symfony framework and a ReactJS based frontend ensure a fully responsive modern UX. Furthermore we use GitLab and Ansible for project management and automating our CI/CD environment. At OpenNovations we’ve created a solution called Aranei built with standard open source tools which generates a state of the art, open web standards based, user interface on top of any existing SQL data structure. Keep the same schema/structure between source system and archiving solution, or to use the notion of a controlled copy, is a much less cumbersome approach, as a one on one data verification can be performed. Not just the UI components themselves are generated by the metadata app modeling engine, also automated test scripts and a data dictionary are generated as part of the data verification process. about this event: https://c3voc.de 00:42:44 https://media.ccc.de/v/3781-sourcery-a-multi-architecture-root-file-system-that-is-mostly-source Sourcery is a program that builds root file systems consisting mostly of Go source code: of the 90,000 files in a typical sourcery root, there are only 12 or so programs. Other programs are compiled on demand to a ramfs-backed file system. Compilation takes a fraction of a second for most programs, and never more than 2 seconds. Once the program is compiled to a statically-linked, tmpfs-based binary, invocation is instantaneous. Because these images are mostly source, they can also be multi-architecture. Binaries present on boot have a path formed from the target os and architecture, e.g. /$OS_$ARCH/bin/init for init. Dynamically compiled binaries are placed in the tmpfs-backed /bin, since these binaries vanish on boot, the path can be simpler. The file system includes the full Go toolchain as well as all source code. Constructing the root file system, including the git clone steps and Go toolchain build, takes under 4 minutes; each additional architecture takes another 90 seconds (to ensure reproducible builds, the Go toolchain builds itself 3 times). Sourcery root file systems are designed for VFAT, a standard for firmware for x86, ARM, and RISC-V. A typical USB stick for sourcery would include a syslinux bootstrap for x86, required for those platforms; a kernel Image file for ARM; and a kernel file for RISC-V: the firmware for ARM and RISC-V is able to find boot kernels without using an on-stick bootstrap. Sourcery may be found at github.com:u-root/sourcery. Sourcery is a program that builds root file systems consisting mostly of Go source code: of the 90,000 files in a typical sourcery root, there are only 12 or so programs. Other programs are compiled on demand to a ramfs-backed file system. Compilation takes a fraction of a second for most programs, and never more than 2 seconds. Once the program is compiled to a statically-linked, tmpfs-based binary, invocation is instantaneous. Because these images are mostly source, they can also be multi-architecture. Binaries present on boot have a path formed from the target os and architecture, e.g. /$OS_$ARCH/bin/init for init. Dynamically compiled binaries are placed in the tmpfs-backed /bin, since these binaries vanish on boot, the path can be simpler. The file system includes the full Go toolchain as well as all source code. Constructing the root file system, including the git clone steps and Go toolchain build, takes under 4 minutes; each additional architecture takes another 90 seconds (to ensure reproducible builds, the Go toolchain builds itself 3 times). Sourcery root file systems are designed for VFAT, a standard for firmware for x86, ARM, and RISC-V. A typical USB stick for sourcery would include a syslinux bootstrap for x86, required for those platforms; a kernel Image file for ARM; and a kernel file for RISC-V: the firmware for ARM and RISC-V is able to find boot kernels without using an on-stick bootstrap. Sourcery may be found at github.com:u-root/sourcery. about this event: https://c3voc.de Sat, 04 Jun 2022 12:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3781-eng-Sourcery_a_multi-architecture_root_file_system_that_is_mostly_source_sd.mp4?1687392844 K5c800uHrlYDh4OqWxcJpQ 2022-06-04T12:00:00+02:00 rminnich No osc22, 3781, 2022, Open Source Build images that boot on multiple architectures, and that include *working* source code for commands, that compile on demand in less than a second, written in Go. Sourcery is a program that builds root file systems consisting mostly of Go source code: of the 90,000 files in a typical sourcery root, there are only 12 or so programs. Other programs are compiled on demand to a ramfs-backed file system. Compilation takes a fraction of a second for most programs, and never more than 2 seconds. Once the program is compiled to a statically-linked, tmpfs-based binary, invocation is instantaneous. Because these images are mostly source, they can also be multi-architecture. Binaries present on boot have a path formed from the target os and architecture, e.g. /$OS_$ARCH/bin/init for init. Dynamically compiled binaries are placed in the tmpfs-backed /bin, since these binaries vanish on boot, the path can be simpler. The file system includes the full Go toolchain as well as all source code. Constructing the root file system, including the git clone steps and Go toolchain build, takes under 4 minutes; each additional architecture takes another 90 seconds (to ensure reproducible builds, the Go toolchain builds itself 3 times). Sourcery root file systems are designed for VFAT, a standard for firmware for x86, ARM, and RISC-V. A typical USB stick for sourcery would include a syslinux bootstrap for x86, required for those platforms; a kernel Image file for ARM; and a kernel file for RISC-V: the firmware for ARM and RISC-V is able to find boot kernels without using an on-stick bootstrap. Sourcery may be found at github.com:u-root/sourcery. Sourcery is a program that builds root file systems consisting mostly of Go source code: of the 90,000 files in a typical sourcery root, there are only 12 or so programs. Other programs are compiled on demand to a ramfs-backed file system. Compilation takes a fraction of a second for most programs, and never more than 2 seconds. Once the program is compiled to a statically-linked, tmpfs-based binary, invocation is instantaneous. Because these images are mostly source, they can also be multi-architecture. Binaries present on boot have a path formed from the target os and architecture, e.g. /$OS_$ARCH/bin/init for init. Dynamically compiled binaries are placed in the tmpfs-backed /bin, since these binaries vanish on boot, the path can be simpler. The file system includes the full Go toolchain as well as all source code. Constructing the root file system, including the git clone steps and Go toolchain build, takes under 4 minutes; each additional architecture takes another 90 seconds (to ensure reproducible builds, the Go toolchain builds itself 3 times). Sourcery root file systems are designed for VFAT, a standard for firmware for x86, ARM, and RISC-V. A typical USB stick for sourcery would include a syslinux bootstrap for x86, required for those platforms; a kernel Image file for ARM; and a kernel file for RISC-V: the firmware for ARM and RISC-V is able to find boot kernels without using an on-stick bootstrap. Sourcery may be found at github.com:u-root/sourcery. about this event: https://c3voc.de 00:30:29 https://media.ccc.de/v/3673-opensuse-board-intro-presentation-discussion Meet the Board, ask questions, discuss topics, have fun Meet the Board, ask questions, discuss topics, have fun about this event: https://c3voc.de Sat, 04 Jun 2022 17:45:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3673-eng-openSUSE_Board_Intro_Presentation_Discussion_sd.mp4?1687321408 J7j7GlkJLmNHtpSgc_tcxg 2022-06-04T17:45:00+02:00 Axel Braun No osc22, 3673, 2022, openSUSE Meet the Board, ask questions, discuss topics, have fun Meet the Board, ask questions, discuss topics, have fun about this event: https://c3voc.de 00:41:20 https://media.ccc.de/v/3874-meeting-with-jitsi-state-of-the-union In this talk Emil will go over some of Jitsi's History, what use cases and larger forces drive its development and where it is headed. Looking forward to seeing you there! In this talk Emil will go over some of Jitsi's History, what use cases and larger forces drive its development and where it is headed. Looking forward to seeing you there! about this event: https://c3voc.de Fri, 03 Jun 2022 18:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3874-eng-Meeting_with_Jitsi_State_of_the_Union_sd.mp4?1687075943 eEV-YZtl6ZUbpGaRi8PfYQ 2022-06-03T18:00:00+02:00 emcho No osc22, 3874, 2022, Keynote In this talk Emil will go over some of Jitsi's History, what use cases and larger forces drive its development and where it is headed. Looking forward to seeing you there! In this talk Emil will go over some of Jitsi's History, what use cases and larger forces drive its development and where it is headed. Looking forward to seeing you there! about this event: https://c3voc.de 00:28:15 https://media.ccc.de/v/3829-a-box-full-of-tools-and-distros 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 Fri, 03 Jun 2022 15:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3829-eng-A_Box_Full_of_Tools_and_Distros_sd.mp4?1687045384 GHWPltWw8l0tMzQjnTU-QQ 2022-06-03T15:30:00+02:00 Dario Faggioli No osc22, 3829, 2022, Cloud and Containers Toolbox and Distrobox on openSUSE MicroOS & Tumbleweed 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 00:35:37 https://media.ccc.de/v/3779-digital-school-abc 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 Thu, 02 Jun 2022 19:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3779-eng-Digital_School_ABC_sd.mp4?1687043306 Hpi5lJgQkGSyCA7sdhBFGg 2022-06-02T19:00:00+02:00 KaratekHD No osc22, 3779, 2022, Open Source All but cloud 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 00:21:49 https://media.ccc.de/v/3796-enhancing-tensorflow-security-secure-software-development-practices-for-developing-a-secure-ml-framework 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 Thu, 02 Jun 2022 18:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3796-eng-Enhancing_TensorFlow_Security_Secure_Software_Development_practices_for_developing_a_secure_ML_framework_sd.mp4?1687040559 k4OK0R20jPXjkP_blOxaQA 2022-06-02T18:00:00+02:00 mihaimaruseac No osc22, 3796, 2022, Keynote 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 00:35:18 https://media.ccc.de/v/3758-opensuse-on-arm This talk is the annual review of openSUSE on Arm, mainly focused on AArch64, but it will also cover armv7 and armv6. At the end, we will have a quick look at the future and where the community could help. This talk is the annual review of openSUSE on Arm, mainly focused on AArch64, but it will also cover armv7 and armv6. At the end, we will have a quick look at the future and where the community could help. about this event: https://c3voc.de Thu, 02 Jun 2022 13:15:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3758-eng-openSUSE_on_Arm_sd.mp4?1687039023 6kQQjjcOp-NX-80yhnJ9bA 2022-06-02T13:15:00+02:00 Guillaume Gardet No osc22, 3758, 2022, openSUSE The annual review This talk is the annual review of openSUSE on Arm, mainly focused on AArch64, but it will also cover armv7 and armv6. At the end, we will have a quick look at the future and where the community could help. This talk is the annual review of openSUSE on Arm, mainly focused on AArch64, but it will also cover armv7 and armv6. At the end, we will have a quick look at the future and where the community could help. about this event: https://c3voc.de 00:15:50 https://media.ccc.de/v/3805-d-installer-project-carving-a-modern-installer D-Installer is the code-name of a experimental project for creating a new YAST-based installer designed to offer reusability, better integration with third-party tools and the possibility of building rich user interfaces over it. In this talk, we will explain the motivation of the YaST Team for creating a new installer and what possibilities this new idea brings. There will be time for diving into some technical details about the project architecture and we will show a live demo! You will hear about D-Bus, web interfaces, YaST and Cockpit. If you are interested in how all those pieces play together, do not hesitate to join us. D-Installer is the code-name of a experimental project for creating a new YAST-based installer designed to offer reusability, better integration with third-party tools and the possibility of building rich user interfaces over it. In this talk, we will explain the motivation of the YaST Team for creating a new installer and what possibilities this new idea brings. There will be time for diving into some technical details about the project architecture and we will show a live demo! You will hear about D-Bus, web interfaces, YaST and Cockpit. If you are interested in how all those pieces play together, do not hesitate to join us. about this event: https://c3voc.de Sat, 04 Jun 2022 12:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3805-eng-D-Installer_Project_Carving_a_Modern_Installer_sd.mp4?1687016069 SsgbEXP-aImiJ95DvgSwxA 2022-06-04T12:30:00+02:00 José Iván López González No osc22, 3805, 2022, openSUSE A new installer based on D-Bus, YaST, Cockpit and web interfaces D-Installer is the code-name of a experimental project for creating a new YAST-based installer designed to offer reusability, better integration with third-party tools and the possibility of building rich user interfaces over it. In this talk, we will explain the motivation of the YaST Team for creating a new installer and what possibilities this new idea brings. There will be time for diving into some technical details about the project architecture and we will show a live demo! You will hear about D-Bus, web interfaces, YaST and Cockpit. If you are interested in how all those pieces play together, do not hesitate to join us. D-Installer is the code-name of a experimental project for creating a new YAST-based installer designed to offer reusability, better integration with third-party tools and the possibility of building rich user interfaces over it. In this talk, we will explain the motivation of the YaST Team for creating a new installer and what possibilities this new idea brings. There will be time for diving into some technical details about the project architecture and we will show a live demo! You will hear about D-Bus, web interfaces, YaST and Cockpit. If you are interested in how all those pieces play together, do not hesitate to join us. about this event: https://c3voc.de 00:24:17 https://media.ccc.de/v/3850-the-art-of-the-linux-desktop Pretty much everything that has ever been designed is some form of balance between form and function, from modified car's to architecture to clothes and even user interfaces. In the modern age of material design, Visual Design Group's and Human Interface Guidelines this balance has very much shifted to be in favor of function over form, an interface that looks good is still important but looks always seem to play a distant second to usability. The purpose of this talk is to explore what happens when you flip that idea and rather then focusing on creating user interfaces that are primarily usable instead focus on creating user interfaces that are works of art with a lesser regard as to how easy they are to use. Fortunately this idea is nothing new, in the late 90's Raster founded the enlightenment desktop inspired by the artistic user interfaces of the games he played growing up, he brought these concepts to the desktop. The advancement of graphics hardware in the mid two thousands lead us to the world of fish tanks inside cubes, wobbly windows and painting fire on the screen. Not because there was any real need or use but because someone could. Sadly since then the world of the Linux desktop has tried to go all professional and many of the fun interesting things have been lost. Pretty much everything that has ever been designed is some form of balance between form and function, from modified car's to architecture to clothes and even user interfaces. In the modern age of material design, Visual Design Group's and Human Interface Guidelines this balance has very much shifted to be in favor of function over form, an interface that looks good is still important but looks always seem to play a distant second to usability. The purpose of this talk is to explore what happens when you flip that idea and rather then focusing on creating user interfaces that are primarily usable instead focus on creating user interfaces that are works of art with a lesser regard as to how easy they are to use. Fortunately this idea is nothing new, in the late 90's Raster founded the enlightenment desktop inspired by the artistic user interfaces of the games he played growing up, he brought these concepts to the desktop. The advancement of graphics hardware in the mid two thousands lead us to the world of fish tanks inside cubes, wobbly windows and painting fire on the screen. Not because there was any real need or use but because someone could. Sadly since then the world of the Linux desktop has tried to go all professional and many of the fun interesting things have been lost. about this event: https://c3voc.de Sat, 04 Jun 2022 11:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3850-eng-The_Art_of_the_Linux_Desktop_sd.mp4?1687007404 9lm_nZ84LRRn2-fKqpT0mw 2022-06-04T11:30:00+02:00 Simon Lees No osc22, 3850, 2022, Open Source Pretty much everything that has ever been designed is some form of balance between form and function, from modified car's to architecture to clothes and even user interfaces. In the modern age of material design, Visual Design Group's and Human Interface Guidelines this balance has very much shifted to be in favor of function over form, an interface that looks good is still important but looks always seem to play a distant second to usability. The purpose of this talk is to explore what happens when you flip that idea and rather then focusing on creating user interfaces that are primarily usable instead focus on creating user interfaces that are works of art with a lesser regard as to how easy they are to use. Fortunately this idea is nothing new, in the late 90's Raster founded the enlightenment desktop inspired by the artistic user interfaces of the games he played growing up, he brought these concepts to the desktop. The advancement of graphics hardware in the mid two thousands lead us to the world of fish tanks inside cubes, wobbly windows and painting fire on the screen. Not because there was any real need or use but because someone could. Sadly since then the world of the Linux desktop has tried to go all professional and many of the fun interesting things have been lost. Pretty much everything that has ever been designed is some form of balance between form and function, from modified car's to architecture to clothes and even user interfaces. In the modern age of material design, Visual Design Group's and Human Interface Guidelines this balance has very much shifted to be in favor of function over form, an interface that looks good is still important but looks always seem to play a distant second to usability. The purpose of this talk is to explore what happens when you flip that idea and rather then focusing on creating user interfaces that are primarily usable instead focus on creating user interfaces that are works of art with a lesser regard as to how easy they are to use. Fortunately this idea is nothing new, in the late 90's Raster founded the enlightenment desktop inspired by the artistic user interfaces of the games he played growing up, he brought these concepts to the desktop. The advancement of graphics hardware in the mid two thousands lead us to the world of fish tanks inside cubes, wobbly windows and painting fire on the screen. Not because there was any real need or use but because someone could. Sadly since then the world of the Linux desktop has tried to go all professional and many of the fun interesting things have been lost. about this event: https://c3voc.de 00:23:53 https://media.ccc.de/v/3808-still-not-superheroes During the last years, the openSUSE infrastructure was improved a lot. But is it perfect now? Of course not - otherwise the Heroes would be bored, and I could not give this talk. And of course, where people work, funny[tm] things happen - please bring your own popcorn ;-) During the last years, the openSUSE infrastructure was improved a lot. But is it perfect now? Of course not - otherwise the Heroes would be bored, and I could not give this talk. And of course, where people work, funny[tm] things happen - please bring your own popcorn ;-) about this event: https://c3voc.de Fri, 03 Jun 2022 19:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3808-eng-Still_not_Superheroes_sd.mp4?1687004688 -n98lnxwSZyaE0JIWEo4WA 2022-06-03T19:30:00+02:00 Christian Boltz No osc22, 3808, 2022, openSUSE During the last years, the openSUSE infrastructure was improved a lot. But is it perfect now? Of course not - otherwise the Heroes would be bored, and I could not give this talk. And of course, where people work, funny[tm] things happen - please bring your own popcorn ;-) During the last years, the openSUSE infrastructure was improved a lot. But is it perfect now? Of course not - otherwise the Heroes would be bored, and I could not give this talk. And of course, where people work, funny[tm] things happen - please bring your own popcorn ;-) about this event: https://c3voc.de 00:21:39 https://media.ccc.de/v/3841-web-asset-security Before downloading a software release, we all know to verify the GPG signature before even trying to unpack that tarball. And when such a signature is not available, we all know to chastise the developer for not taking security seriously. But what happens with deployed web resources? How can these be verified before we trust them with our secure data? I would like to show a proof-of-concept of using out-of-band verification (aka, DNS) of web content (.js, .html, .jpeg, etc) prior to allowing it to execute and trusting it with our data. Before downloading a software release, we all know to verify the GPG signature before even trying to unpack that tarball. And when such a signature is not available, we all know to chastise the developer for not taking security seriously. But what happens with deployed web resources? How can these be verified before we trust them with our secure data? I would like to show a proof-of-concept of using out-of-band verification (aka, DNS) of web content (.js, .html, .jpeg, etc) prior to allowing it to execute and trusting it with our data. about this event: https://c3voc.de Fri, 03 Jun 2022 19:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3841-eng-Web_asset_security_sd.mp4?1687003952 DaQkPrKgN4jHNKuBQBessg 2022-06-03T19:30:00+02:00 Adam Majer No osc22, 3841, 2022, New Technologies and how to verify that Javascript before you trust your data to it Before downloading a software release, we all know to verify the GPG signature before even trying to unpack that tarball. And when such a signature is not available, we all know to chastise the developer for not taking security seriously. But what happens with deployed web resources? How can these be verified before we trust them with our secure data? I would like to show a proof-of-concept of using out-of-band verification (aka, DNS) of web content (.js, .html, .jpeg, etc) prior to allowing it to execute and trusting it with our data. Before downloading a software release, we all know to verify the GPG signature before even trying to unpack that tarball. And when such a signature is not available, we all know to chastise the developer for not taking security seriously. But what happens with deployed web resources? How can these be verified before we trust them with our secure data? I would like to show a proof-of-concept of using out-of-band verification (aka, DNS) of web content (.js, .html, .jpeg, etc) prior to allowing it to execute and trusting it with our data. about this event: https://c3voc.de 00:26:34 https://media.ccc.de/v/3826-uyuni-saltboot-automated-image-deployment-and-lifecycle-with-uyuni Deploying images is ever evolving topic. Although much of the deployments today are concerned with containers, base systems for container host are somehow needed to be deployed as well. Let me present Saltboot, part of Uyuni stack. Saltboot is building on SaltStack to make image deployment secure and together with Uyuni provides complete image lifecycle and management - from image building, staging to deployment on target machines. Deploying images is ever evolving topic. Although much of the deployments today are concerned with containers, base systems for container host are somehow needed to be deployed as well. Let me present Saltboot, part of Uyuni stack. Saltboot is building on SaltStack to make image deployment secure and together with Uyuni provides complete image lifecycle and management - from image building, staging to deployment on target machines. about this event: https://c3voc.de Fri, 03 Jun 2022 18:45:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3826-eng-Uyuni_Saltboot_-_automated_image_deployment_and_lifecycle_with_Uyuni_sd.mp4?1687000181 9Y4jy24KZGBC7J3ltwTs2A 2022-06-03T18:45:00+02:00 Ondrej Holecek No osc22, 3826, 2022, Open Source Deploying filesystem images on real hardware or VMs securely and with complete control Deploying images is ever evolving topic. Although much of the deployments today are concerned with containers, base systems for container host are somehow needed to be deployed as well. Let me present Saltboot, part of Uyuni stack. Saltboot is building on SaltStack to make image deployment secure and together with Uyuni provides complete image lifecycle and management - from image building, staging to deployment on target machines. Deploying images is ever evolving topic. Although much of the deployments today are concerned with containers, base systems for container host are somehow needed to be deployed as well. Let me present Saltboot, part of Uyuni stack. Saltboot is building on SaltStack to make image deployment secure and together with Uyuni provides complete image lifecycle and management - from image building, staging to deployment on target machines. about this event: https://c3voc.de 00:45:41 https://media.ccc.de/v/3859-state-of-transactional-update **transactional-update** is the openSUSE way of a **Transactional Operating System update** and a core component of _openSUSE MicroOS_ / _Kubic_ and _SLE Micro_, making sure updates can be applied safely without affecting the currently running system. It's also supposed to play an important component in the future ALP. At lot of things have changed internally since the last talk at oSC19: The core functionality has been **rewritten in C++** (formerly Bash), including a **C++ and C API** and a **D-Bus interface**. From a user's perspective the transactional-update command line interface still looks the same, but we now have **Cockpit** and **dnf integration**. This talk will - give a **short overview of transactional-update** for those new to the concept. - introduce `tukit`, the command line interface for the API functionality. - present the new **Cockpit** interface for transactional-update. - present the **dnf** integration. - give an overview over other changes (SELinux support, Kernel Live Patching). - and we should also have some minutes left for questions and discussions. **transactional-update** is the openSUSE way of a **Transactional Operating System update** and a core component of _openSUSE MicroOS_ / _Kubic_ and _SLE Micro_, making sure updates can be applied safely without affecting the currently running system. It's also supposed to play an important component in the future ALP. At lot of things have changed internally since the last talk at oSC19: The core functionality has been **rewritten in C++** (formerly Bash), including a **C++ and C API** and a **D-Bus interface**. From a user's perspective the transactional-update command line interface still looks the same, but we now have **Cockpit** and **dnf integration**. This talk will - give a **short overview of transactional-update** for those new to the concept. - introduce `tukit`, the command line interface for the API functionality. - present the new **Cockpit** interface for transactional-update. - present the **dnf** integration. - give an overview over other changes (SELinux support, Kernel Live Patching). - and we should also have some minutes left for questions and discussions. about this event: https://c3voc.de Sat, 04 Jun 2022 12:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3859-eng-State_of_transactional-update_sd.mp4?1687012378 2mCtUN8KA579-f4OICsiqQ 2022-06-04T12:00:00+02:00 Ignaz Forster No osc22, 3859, 2022, openSUSE **transactional-update** is the openSUSE way of a **Transactional Operating System update** and a core component of _openSUSE MicroOS_ / _Kubic_ and _SLE Micro_, making sure updates can be applied safely without affecting the currently running system. It's also supposed to play an important component in the future ALP. At lot of things have changed internally since the last talk at oSC19: The core functionality has been **rewritten in C++** (formerly Bash), including a **C++ and C API** and a **D-Bus interface**. From a user's perspective the transactional-update command line interface still looks the same, but we now have **Cockpit** and **dnf integration**. This talk will - give a **short overview of transactional-update** for those new to the concept. - introduce `tukit`, the command line interface for the API functionality. - present the new **Cockpit** interface for transactional-update. - present the **dnf** integration. - give an overview over other changes (SELinux support, Kernel Live Patching). - and we should also have some minutes left for questions and discussions. **transactional-update** is the openSUSE way of a **Transactional Operating System update** and a core component of _openSUSE MicroOS_ / _Kubic_ and _SLE Micro_, making sure updates can be applied safely without affecting the currently running system. It's also supposed to play an important component in the future ALP. At lot of things have changed internally since the last talk at oSC19: The core functionality has been **rewritten in C++** (formerly Bash), including a **C++ and C API** and a **D-Bus interface**. From a user's perspective the transactional-update command line interface still looks the same, but we now have **Cockpit** and **dnf integration**. This talk will - give a **short overview of transactional-update** for those new to the concept. - introduce `tukit`, the command line interface for the API functionality. - present the new **Cockpit** interface for transactional-update. - present the **dnf** integration. - give an overview over other changes (SELinux support, Kernel Live Patching). - and we should also have some minutes left for questions and discussions. about this event: https://c3voc.de 00:27:29 https://media.ccc.de/v/3814-learning-to-package-in-opensuse 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 Fri, 03 Jun 2022 13:50:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3814-eng-Learning_to_Package_in_openSUSE_sd.mp4?1686992331 0i5-rNfnL8l4cruMOHloRg 2022-06-03T13:50:00+02:00 Emily Gonyer No osc22, 3814, 2022, openSUSE in OBS 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 00:07:59 https://media.ccc.de/v/3749-microos-tiu We have several ways to install and update openSUSE distributions, standard with zypper, atomic with transactional-update or using disk images created with kiwi or similar tools. But this are all RPM based. In some scenarios, it would be good to have an image based installation and update mechanism (image means /usr, not a full disk image). A PoC is MicroOS TIU (https://github.com/thkukuk/tiu), which allows to use either btrfs snapshots or several partitions (usrAB) for installation and update. This talk will give some insight into it. The current status, the problems, what it means for packaging, etc. We have several ways to install and update openSUSE distributions, standard with zypper, atomic with transactional-update or using disk images created with kiwi or similar tools. But this are all RPM based. In some scenarios, it would be good to have an image based installation and update mechanism (image means /usr, not a full disk image). A PoC is MicroOS TIU (https://github.com/thkukuk/tiu), which allows to use either btrfs snapshots or several partitions (usrAB) for installation and update. This talk will give some insight into it. The current status, the problems, what it means for packaging, etc. about this event: https://c3voc.de Sat, 04 Jun 2022 13:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3749-eng-MicroOS_TIU_sd.mp4?1687019327 EO0Vot3wVKWlF7KS9chEvQ 2022-06-04T13:00:00+02:00 Thorsten Kukuk No osc22, 3749, 2022, New Technologies Transactional Image Update We have several ways to install and update openSUSE distributions, standard with zypper, atomic with transactional-update or using disk images created with kiwi or similar tools. But this are all RPM based. In some scenarios, it would be good to have an image based installation and update mechanism (image means /usr, not a full disk image). A PoC is MicroOS TIU (https://github.com/thkukuk/tiu), which allows to use either btrfs snapshots or several partitions (usrAB) for installation and update. This talk will give some insight into it. The current status, the problems, what it means for packaging, etc. We have several ways to install and update openSUSE distributions, standard with zypper, atomic with transactional-update or using disk images created with kiwi or similar tools. But this are all RPM based. In some scenarios, it would be good to have an image based installation and update mechanism (image means /usr, not a full disk image). A PoC is MicroOS TIU (https://github.com/thkukuk/tiu), which allows to use either btrfs snapshots or several partitions (usrAB) for installation and update. This talk will give some insight into it. The current status, the problems, what it means for packaging, etc. about this event: https://c3voc.de 00:40:46 https://media.ccc.de/v/3799-getting-the-most-of-autoyast-in-2022 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 Fri, 03 Jun 2022 15:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3799-eng-Getting_the_most_of_AutoYaST_in_2022_sd.mp4?1686990063 V8534QrV6XXOAR3mAEfIEw 2022-06-03T15:00:00+02:00 Imobach González Sosa No osc22, 3799, 2022, openSUSE Presenting some recent features you may have missed 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 00:24:36 https://media.ccc.de/v/3790-making-a-switch-from-docker-to-podman-in-development-environment On an example of PMM (Percona Monitoring and Management) opensource project I would like to show how to use podman instead of docker in software development process. We would go throw the basic (how to configure it) and discuss the changes required in build scripts, environment and etc. This will cover docker (run, build), docker-compose and briefly minikube to be replaced or use podman. [presentation slides](https://denisok.github.io/oSC/switch_docker_podman_dev_env.html) On an example of PMM (Percona Monitoring and Management) opensource project I would like to show how to use podman instead of docker in software development process. We would go throw the basic (how to configure it) and discuss the changes required in build scripts, environment and etc. This will cover docker (run, build), docker-compose and briefly minikube to be replaced or use podman. [presentation slides](https://denisok.github.io/oSC/switch_docker_podman_dev_env.html) about this event: https://c3voc.de Fri, 03 Jun 2022 16:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3790-eng-making_a_switch_from_docker_to_podman_in_development_environment_sd.mp4?1686992224 aTbwzAQf2_92HOscr3VlVQ 2022-06-03T16:30:00+02:00 Denys Kondratenko No osc22, 3790, 2022, Cloud and Containers how to configure env to use podman On an example of PMM (Percona Monitoring and Management) opensource project I would like to show how to use podman instead of docker in software development process. We would go throw the basic (how to configure it) and discuss the changes required in build scripts, environment and etc. This will cover docker (run, build), docker-compose and briefly minikube to be replaced or use podman. [presentation slides](https://denisok.github.io/oSC/switch_docker_podman_dev_env.html) On an example of PMM (Percona Monitoring and Management) opensource project I would like to show how to use podman instead of docker in software development process. We would go throw the basic (how to configure it) and discuss the changes required in build scripts, environment and etc. This will cover docker (run, build), docker-compose and briefly minikube to be replaced or use podman. [presentation slides](https://denisok.github.io/oSC/switch_docker_podman_dev_env.html) about this event: https://c3voc.de 00:27:58 https://media.ccc.de/v/3844-usrmerge-and-beyond A traditional Linux file system tree in the root file system has quite a number of directories with special purpose, documented in the Filesystem Hierarchy Standard (FHS). An operating system installation by default populates most of those directories with different kinds of files, e.g. by means of a package manager. When looking closer this theoretical order is quite a mess in practice. Alternative approaches to manage and update software components of the operating system such as MicroOS reveal the inconsistencies and require stricter separation of different types of files. This talk analyzes where we're coming from, how the tree looks today and where we're heading. The talk will be based on https://lnussel.github.io/2020/12/16/fslayout/ A traditional Linux file system tree in the root file system has quite a number of directories with special purpose, documented in the Filesystem Hierarchy Standard (FHS). An operating system installation by default populates most of those directories with different kinds of files, e.g. by means of a package manager. When looking closer this theoretical order is quite a mess in practice. Alternative approaches to manage and update software components of the operating system such as MicroOS reveal the inconsistencies and require stricter separation of different types of files. This talk analyzes where we're coming from, how the tree looks today and where we're heading. The talk will be based on https://lnussel.github.io/2020/12/16/fslayout/ about this event: https://c3voc.de Sat, 04 Jun 2022 15:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3844-eng-usrmerge_and_beyond_sd.mp4?1686967383 YzCKCiMKUgEMbQSAZYK1KQ 2022-06-04T15:00:00+02:00 Ludwig Nussel No osc22, 3844, 2022, openSUSE what's happening to the file system layout? A traditional Linux file system tree in the root file system has quite a number of directories with special purpose, documented in the Filesystem Hierarchy Standard (FHS). An operating system installation by default populates most of those directories with different kinds of files, e.g. by means of a package manager. When looking closer this theoretical order is quite a mess in practice. Alternative approaches to manage and update software components of the operating system such as MicroOS reveal the inconsistencies and require stricter separation of different types of files. This talk analyzes where we're coming from, how the tree looks today and where we're heading. The talk will be based on https://lnussel.github.io/2020/12/16/fslayout/ A traditional Linux file system tree in the root file system has quite a number of directories with special purpose, documented in the Filesystem Hierarchy Standard (FHS). An operating system installation by default populates most of those directories with different kinds of files, e.g. by means of a package manager. When looking closer this theoretical order is quite a mess in practice. Alternative approaches to manage and update software components of the operating system such as MicroOS reveal the inconsistencies and require stricter separation of different types of files. This talk analyzes where we're coming from, how the tree looks today and where we're heading. The talk will be based on https://lnussel.github.io/2020/12/16/fslayout/ about this event: https://c3voc.de 00:17:18 https://media.ccc.de/v/3770-opensource-secure-yes-if-you-audit-it Tales in a life of a product security engineer making Open Source software more secure one bit at time. In this session, I will talk about what does it mean to be a product security engineer and how SUSE security team audits can help Open Source community in having a better security posture. Tales in a life of a product security engineer making Open Source software more secure one bit at time. In this session, I will talk about what does it mean to be a product security engineer and how SUSE security team audits can help Open Source community in having a better security posture. about this event: https://c3voc.de Fri, 03 Jun 2022 20:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3770-eng-opensource_secure_Yes_if_you_audit_it_sd.mp4?1686965176 JbvqnSD51Rr7cWYjDakvuQ 2022-06-03T20:00:00+02:00 Paolo Perego No osc22, 3770, 2022, Open Source Tales in a life of a product security engineer making opensource software more secure one bit at time. Tales in a life of a product security engineer making Open Source software more secure one bit at time. In this session, I will talk about what does it mean to be a product security engineer and how SUSE security team audits can help Open Source community in having a better security posture. Tales in a life of a product security engineer making Open Source software more secure one bit at time. In this session, I will talk about what does it mean to be a product security engineer and how SUSE security team audits can help Open Source community in having a better security posture. about this event: https://c3voc.de 00:18:53 https://media.ccc.de/v/3734-almost-two-years-of-yast-news 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 Fri, 03 Jun 2022 15:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3734-eng-Almost_Two_Years_of_YaST_News_sd.mp4?1686957235 55H2q1hx8bvlUWvHx798lg 2022-06-03T15:30:00+02:00 Ancor González Sosa No osc22, 3734, 2022, openSUSE Recent changes and future plans at YaSTland 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 00:37:06 https://media.ccc.de/v/3691-sudo-1-9 Sudo is used by millions to control and log administrator access to systems, but using only the default configuration, there are plenty of blind spots. Using the latest features in sudo lets you watch some functions that previously were blind spots and you can also control access to them. There were several minor and major changes since the 1.9.0 release that I discussed in my previous FOSDEM talks. Sudo is used by millions to control and log administrator access to systems, but using only the default configuration, there are plenty of blind spots. Using the latest features in sudo lets you watch some functions that previously were blind spots and you can also control access to them. There were several minor and major changes since the 1.9.0 release that I discussed in my previous FOSDEM talks. about this event: https://c3voc.de Fri, 03 Jun 2022 18:45:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3691-eng-Sudo_19_sd.mp4?1686963883 uRuRimsstzbfLI-QF06YIA 2022-06-03T18:45:00+02:00 Peter Czanik No osc22, 3691, 2022, New Technologies watch and control your blind spots Sudo is used by millions to control and log administrator access to systems, but using only the default configuration, there are plenty of blind spots. Using the latest features in sudo lets you watch some functions that previously were blind spots and you can also control access to them. There were several minor and major changes since the 1.9.0 release that I discussed in my previous FOSDEM talks. Sudo is used by millions to control and log administrator access to systems, but using only the default configuration, there are plenty of blind spots. Using the latest features in sudo lets you watch some functions that previously were blind spots and you can also control access to them. There were several minor and major changes since the 1.9.0 release that I discussed in my previous FOSDEM talks. about this event: https://c3voc.de 00:30:51 https://media.ccc.de/v/3905-new-git-based-workflow-for-factory-packages The Open Build Service has new support to allow developing packages directly in git repositories. This means that entire source management would be handed over to some pagure, gitlab or gerrit instance as origin of trust. The talk will describe possible setups, workflows and development scenarios. Including an open discussion what should we aim for our main distributions. The Open Build Service has new support to allow developing packages directly in git repositories. This means that entire source management would be handed over to some pagure, gitlab or gerrit instance as origin of trust. The talk will describe possible setups, workflows and development scenarios. Including an open discussion what should we aim for our main distributions. about this event: https://c3voc.de Fri, 03 Jun 2022 17:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3905-eng-New_git_based_workflow_for_Factory_packages_sd.mp4?1686960184 tXqoR1-UIS9PKBiPNkN92A 2022-06-03T17:30:00+02:00 Adrian Schröter No osc22, 3905, 2022, Open Source The Open Build Service has new support to allow developing packages directly in git repositories. This means that entire source management would be handed over to some pagure, gitlab or gerrit instance as origin of trust. The talk will describe possible setups, workflows and development scenarios. Including an open discussion what should we aim for our main distributions. The Open Build Service has new support to allow developing packages directly in git repositories. This means that entire source management would be handed over to some pagure, gitlab or gerrit instance as origin of trust. The talk will describe possible setups, workflows and development scenarios. Including an open discussion what should we aim for our main distributions. about this event: https://c3voc.de 00:39:49 https://media.ccc.de/v/3895-the-opensuse-bar-story This talk will go over the history of the openSUSE Bar. How it started and what it has done. This talk will go over the history of the openSUSE Bar. How it started and what it has done. about this event: https://c3voc.de Sat, 04 Jun 2022 13:55:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3895-eng-The_openSUSE_Bar_Story_sd.mp4?1686930987 or2BZLy6Y1wCKA7w5jTB8w 2022-06-04T13:55:00+02:00 No osc22, 3895, 2022, Community This talk will go over the history of the openSUSE Bar. How it started and what it has done. This talk will go over the history of the openSUSE Bar. How it started and what it has done. about this event: https://c3voc.de 00:12:33 https://media.ccc.de/v/3700-collaboration-instead-of-competition Default community distributions are running in the same issues for special architectures. Every Linux distribution has got mostly separate maintainers and hardware distributors are handling these communities really often disconnected. That has been identified also for the architecture s390x. Therefore, openSUSE, Fedora, Debian, SUSE, Canonical (Ubuntu) and Red Hat have established together with IBM a Linux Distributions Working Group for a better collaboration together and with the goal to achieve better support. In this presentation, you should receive an overview of a good collaboration between Linux distributions and what you can achieve together with such a Working Group. Default community distributions are running in the same issues for special architectures. Every Linux distribution has got mostly separate maintainers and hardware distributors are handling these communities really often disconnected. That has been identified also for the architecture s390x. Therefore, openSUSE, Fedora, Debian, SUSE, Canonical (Ubuntu) and Red Hat have established together with IBM a Linux Distributions Working Group for a better collaboration together and with the goal to achieve better support. In this presentation, you should receive an overview of a good collaboration between Linux distributions and what you can achieve together with such a Working Group. about this event: https://c3voc.de Sat, 04 Jun 2022 12:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3700-eng-Collaboration_instead_of_Competition_sd.mp4?1686929186 trECigpijYwzw86SSzcfXg 2022-06-04T12:30:00+02:00 Sarah Julia Kriesch No osc22, 3700, 2022, Community The Linux Distributions Working Group at the Open Mainframe Project Default community distributions are running in the same issues for special architectures. Every Linux distribution has got mostly separate maintainers and hardware distributors are handling these communities really often disconnected. That has been identified also for the architecture s390x. Therefore, openSUSE, Fedora, Debian, SUSE, Canonical (Ubuntu) and Red Hat have established together with IBM a Linux Distributions Working Group for a better collaboration together and with the goal to achieve better support. In this presentation, you should receive an overview of a good collaboration between Linux distributions and what you can achieve together with such a Working Group. Default community distributions are running in the same issues for special architectures. Every Linux distribution has got mostly separate maintainers and hardware distributors are handling these communities really often disconnected. That has been identified also for the architecture s390x. Therefore, openSUSE, Fedora, Debian, SUSE, Canonical (Ubuntu) and Red Hat have established together with IBM a Linux Distributions Working Group for a better collaboration together and with the goal to achieve better support. In this presentation, you should receive an overview of a good collaboration between Linux distributions and what you can achieve together with such a Working Group. about this event: https://c3voc.de 00:28:49 https://media.ccc.de/v/3694-a-new-distribution-opensuse-leap-micro openSUSE Leap Micro is a new distribution based on SUSE Linux Enterprise Micro with the main purpose to be a host-os with minimal footprint which fits well the app-centric world. A small foot print, focus on the EDGE as well as data center, containerization and virtual machines, whatever flies your app. Leap Micro has a 6 months release cycle with support lasting until the next release or up to 4 years of support with a migration to SLE Micro. openSUSE Leap Micro is a new distribution based on SUSE Linux Enterprise Micro with the main purpose to be a host-os with minimal footprint which fits well the app-centric world. A small foot print, focus on the EDGE as well as data center, containerization and virtual machines, whatever flies your app. Leap Micro has a 6 months release cycle with support lasting until the next release or up to 4 years of support with a migration to SLE Micro. about this event: https://c3voc.de Fri, 03 Jun 2022 17:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3694-eng-A_new_distribution_openSUSE_Leap_Micro_sd.mp4?1686899491 gmJclEgp0JCL8YmrV-gusw 2022-06-03T17:00:00+02:00 Lubos Kocman No osc22, 3694, 2022, openSUSE openSUSE Leap Micro is a new distribution based on SUSE Linux Enterprise Micro with the main purpose to be a host-os with minimal footprint which fits well the app-centric world. A small foot print, focus on the EDGE as well as data center, containerization and virtual machines, whatever flies your app. Leap Micro has a 6 months release cycle with support lasting until the next release or up to 4 years of support with a migration to SLE Micro. openSUSE Leap Micro is a new distribution based on SUSE Linux Enterprise Micro with the main purpose to be a host-os with minimal footprint which fits well the app-centric world. A small foot print, focus on the EDGE as well as data center, containerization and virtual machines, whatever flies your app. Leap Micro has a 6 months release cycle with support lasting until the next release or up to 4 years of support with a migration to SLE Micro. about this event: https://c3voc.de 00:18:52 https://media.ccc.de/v/3883-alp-roast-an-open-discussion-with-the-alp-steering-committee 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 Fri, 03 Jun 2022 13:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3883-eng-ALP_Roast_-_An_open_discussion_with_the_ALP_Steering_Committee_sd.mp4?1686894305 N16ULuPQGSmFHpxN0YWyKQ 2022-06-03T13:00:00+02:00 Douglas DeMaio No osc22, 3883, 2022, openSUSE 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 00:40:49 https://media.ccc.de/v/3802-speedy-distro-porting-via-the-cpu-command 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 Fri, 03 Jun 2022 12:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3802-eng-Speedy_Distro_Porting_via_the_cpu_Command_sd.mp4?1686883863 twjaYLfC9k1rsdz-QRm1SQ 2022-06-03T12:30:00+02:00 Daniel Maslowski No osc22, 3802, 2022, New Technologies 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 00:23:38 https://media.ccc.de/v/3773-leap-is-dead-we-need-a-new-development-model 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 Fri, 03 Jun 2022 12:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3773-eng-Leap_is_dead_-_We_need_a_new_development_model_sd.mp4?1686884523 iIVPisduwdbUIo0tVahrxA 2022-06-03T12:30:00+02:00 Axel Braun No osc22, 3773, 2022, openSUSE 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 00:27:09 https://media.ccc.de/v/3764-put-all-your-iot-boot-management-in-one-place-the-centre 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 Fri, 03 Jun 2022 12:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3764-eng-Put_all_your_IoT_boot_management_in_one_place_--_the_centre_sd.mp4?1686879552 moZXQzDw63pSo4eXGuprJA 2022-06-03T12:00:00+02:00 rminnich No osc22, 3764, 2022, Embedded Systems and Edge Computing Are you sick of editing 8 files, and loading 5 daemons, for your network boots? Do you not care what a DHCP lease is? This one program can manage all aspects of IoT. 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 00:21:49 https://media.ccc.de/v/3862-dns 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 Fri, 03 Jun 2022 12:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3862-eng-DNS_sd.mp4?1686877935 KsipWzrDRfKlylRITwMPSg 2022-06-03T12:00:00+02:00 Adam Majer No osc22, 3862, 2022, Open Source A distributed directory that runs the Internet 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 00:26:36 https://media.ccc.de/v/3719-will-my-hardware-work-with-opensuse 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 Fri, 03 Jun 2022 11:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3719-eng-Will_my_hardware_work_with_openSUSE_sd.mp4?1686874465 jIxzW8zqRMmTzOy4IYH42g 2022-06-03T11:30:00+02:00 rainerkoenig No osc22, 3719, 2022, openSUSE Don't be afraid of the kernel 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 00:31:45 https://media.ccc.de/v/3820-shortening-the-feedback-loops-between-r-d-and-the-real-world-with-opensuse-and-openqa 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 Thu, 02 Jun 2022 20:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3820-eng-Shortening_the_feedback_loops_between_R_D_and_the_real_world_with_openSUSE_and_openQA_sd.mp4?1686869281 WdqH-rMTs__Kjx2DuoP3NA 2022-06-02T20:00:00+02:00 Santiago Zarate No osc22, 3820, 2022, Open Source 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 00:38:49 https://media.ccc.de/v/3838-open-suse-product-security 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 Thu, 02 Jun 2022 17:15:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3838-eng-open_SUSE_Product_security_sd.mp4?1686864401 mnZ81NZMB4i3k2XBpojqRg 2022-06-02T17:15:00+02:00 Marcus Meissner No osc22, 3838, 2022, openSUSE a short overview 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 00:34:03 https://media.ccc.de/v/3784-hpc-deployment-with-warewulf4 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 Thu, 02 Jun 2022 17:15:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3784-eng-HPC_deployment_with_warewulf4_sd.mp4?1686864504 8dTtPUa_5axEFzrkTXLCFg 2022-06-02T17:15:00+02:00 mslacken No osc22, 3784, 2022, New Technologies Get HPC cluster installed in minutes 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 00:17:49 https://media.ccc.de/v/3710-remote-attestation-in-microos 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 Thu, 02 Jun 2022 16:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3710-eng-Remote_Attestation_in_MicroOS_sd.mp4?1686862112 bNE2PlcQ8OoE86-MbviU_Q 2022-06-02T16:30:00+02:00 Alberto Planas No osc22, 3710, 2022, New Technologies Measuring the health of our system with a TPM 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 00:35:08 https://media.ccc.de/v/3752-the-suse-qe-tools-team-who-we-are-and-what-we-do 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 Thu, 02 Jun 2022 15:45:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3752-eng-The_SUSE_QE_Tools_team_-_Who_we_are_and_what_we_do_sd.mp4?1686855931 wb7mK5IEl8920hEMxiMfYA 2022-06-02T15:45:00+02:00 Oliver Kurz No osc22, 3752, 2022, Open Source 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 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 00:21:39 https://media.ccc.de/v/3688-sle-bci-container-images-for-development-and-production 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 Thu, 02 Jun 2022 15:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3688-eng-SLE_BCI_Container_Images_for_development_and_production_sd.mp4?1686853126 7143itZrfkOD8BYi4Vh2dg 2022-06-02T15:30:00+02:00 Alexander Herzig No osc22, 3688, 2022, Cloud and Containers 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 00:32:09 https://media.ccc.de/v/3728-security-for-not-only-opensuse-developers General security recommendations for openSUSE developers. This includes specific recommendations on how to package software in a more secure ways and how to create a developer setup that is secure. For this we will shed some light on the specific challenges and quirks of the tool chains we use and how they relate to security. General security recommendations for openSUSE developers. This includes specific recommendations on how to package software in a more secure ways and how to create a developer setup that is secure. For this we will shed some light on the specific challenges and quirks of the tool chains we use and how they relate to security. about this event: https://c3voc.de Thu, 02 Jun 2022 15:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3728-eng-Security_for_not_only_openSUSE_developers_sd.mp4?1686849154 tWbuwzulrFQ9-t8aSkIgbQ 2022-06-02T15:00:00+02:00 Johannes Segitz No osc22, 3728, 2022, Open Source General security recommendations for openSUSE developers. This includes specific recommendations on how to package software in a more secure ways and how to create a developer setup that is secure. For this we will shed some light on the specific challenges and quirks of the tool chains we use and how they relate to security. General security recommendations for openSUSE developers. This includes specific recommendations on how to package software in a more secure ways and how to create a developer setup that is secure. For this we will shed some light on the specific challenges and quirks of the tool chains we use and how they relate to security. about this event: https://c3voc.de 00:34:56 https://media.ccc.de/v/3761-reporting-bugs-for-opensuse-leap The way how we build openSUSE Leap has changed, so did the way how we report issues against it. This lightning talk will show you how to correctly report bugs for openSUSE Leap. https://en.opensuse.org/openSUSE:Submitting_bug_reports The way how we build openSUSE Leap has changed, so did the way how we report issues against it. This lightning talk will show you how to correctly report bugs for openSUSE Leap. https://en.opensuse.org/openSUSE:Submitting_bug_reports about this event: https://c3voc.de Thu, 02 Jun 2022 14:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3761-eng-Reporting_bugs_for_openSUSE_Leap_sd.mp4?1686847073 8HtHgjhfa8B0WsiS3Dic-w 2022-06-02T14:00:00+02:00 Lubos Kocman No osc22, 3761, 2022, openSUSE The way how we build openSUSE Leap has changed, so did the way how we report issues against it. This lightning talk will show you how to correctly report bugs for openSUSE Leap. https://en.opensuse.org/openSUSE:Submitting_bug_reports The way how we build openSUSE Leap has changed, so did the way how we report issues against it. This lightning talk will show you how to correctly report bugs for openSUSE Leap. https://en.opensuse.org/openSUSE:Submitting_bug_reports about this event: https://c3voc.de 00:10:03 https://media.ccc.de/v/3793-opensuseway-status-running-other-platforms Whats up with openSUSEway? Current status. Sharing the results of running openSUSEway/sway on openSUSE MicroOS Desktop and Fedora. https://denisok.github.io/oSC/oSC22-openSUSEway.html Whats up with openSUSEway? Current status. Sharing the results of running openSUSEway/sway on openSUSE MicroOS Desktop and Fedora. https://denisok.github.io/oSC/oSC22-openSUSEway.html about this event: https://c3voc.de Thu, 02 Jun 2022 13:50:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3793-eng-openSUSEway_status_running_other_platforms_sd.mp4?1686847019 uSCesvyU3X11HmXkv5GlVQ 2022-06-02T13:50:00+02:00 Denys Kondratenko No osc22, 3793, 2022, openSUSE sway tilling window manager Whats up with openSUSEway? Current status. Sharing the results of running openSUSEway/sway on openSUSE MicroOS Desktop and Fedora. https://denisok.github.io/oSC/oSC22-openSUSEway.html Whats up with openSUSEway? Current status. Sharing the results of running openSUSEway/sway on openSUSE MicroOS Desktop and Fedora. https://denisok.github.io/oSC/oSC22-openSUSEway.html about this event: https://c3voc.de 00:11:20 https://media.ccc.de/v/3716-the-year-of-the-linux-desktop Since long every year is announced to be the "year of the Linux desktop", and every year there is no real breakthrough. In this talk I will look at some reasons why there is no breakthrough yet. **About me:** Software developer, 25+ years Linux. I was the person responsible for Linux on the Desktop at the last European PC manufacturer (Fujtsu) for 17 years and can tell from my own experience why Linux on the desktop is an ongoing struggle. Since long every year is announced to be the "year of the Linux desktop", and every year there is no real breakthrough. In this talk I will look at some reasons why there is no breakthrough yet. **About me:** Software developer, 25+ years Linux. I was the person responsible for Linux on the Desktop at the last European PC manufacturer (Fujtsu) for 17 years and can tell from my own experience why Linux on the desktop is an ongoing struggle. about this event: https://c3voc.de Thu, 02 Jun 2022 13:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3716-eng-The_year_of_the_Linux_desktop_sd.mp4?1686842325 ZBzc32enRQV86YjW2tfNTw 2022-06-02T13:00:00+02:00 rainerkoenig No osc22, 3716, 2022, Open Source Why are we still waiting for the breakthrough? Since long every year is announced to be the "year of the Linux desktop", and every year there is no real breakthrough. In this talk I will look at some reasons why there is no breakthrough yet. **About me:** Software developer, 25+ years Linux. I was the person responsible for Linux on the Desktop at the last European PC manufacturer (Fujtsu) for 17 years and can tell from my own experience why Linux on the desktop is an ongoing struggle. Since long every year is announced to be the "year of the Linux desktop", and every year there is no real breakthrough. In this talk I will look at some reasons why there is no breakthrough yet. **About me:** Software developer, 25+ years Linux. I was the person responsible for Linux on the Desktop at the last European PC manufacturer (Fujtsu) for 17 years and can tell from my own experience why Linux on the desktop is an ongoing struggle. about this event: https://c3voc.de 00:38:33 https://media.ccc.de/v/3886-a-fork-in-the-road-by-opensuse-board The board will kick off the conference and give some options important to be discussed throughout the event. The board will kick off the conference and give some options important to be discussed throughout the event. about this event: https://c3voc.de Thu, 02 Jun 2022 11:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3886-eng-A_Fork_in_the_Road_by_openSUSE_Board_sd.mp4?1654533892 -Xv3vXybsjB9cpvTksN4-A 2022-06-02T11:30:00+02:00 Douglas DeMaio No osc22, 3886, 2022 The board will kick off the conference and give some options important to be discussed throughout the event. The board will kick off the conference and give some options important to be discussed throughout the event. about this event: https://c3voc.de 00:23:30 https://media.ccc.de/v/3877-as-i-was-saying ** Required Magic's Carpet: How we designed a mass deployment system for Linux. ** In 2014 we started working with a major Irish bank to help them with a project to upgrade 7,500 Linux workstations across all of their branches. Over the next two years we completed that task - not just once - but on a weekly basis, across 900 locations - with just **two** people, and **zero** site visits. Our discoveries of their systems and techniques led us to build "Carpet" (formally known as "Snoopea"), a tool to rapidly roll out - and maintain - Linux systems across a wide area network. The systems don't have to be desktop based either - so long as the devices are network connected, Carpet can deploy IOT, Server and virtual machines too. This high level talk is an overview of the the journey to take the original CLI based system to a modern, web based tool - including how we used Kiwi (and image builder), and Nuitka (a python compiler) to build certain components. We'll start from the beginning for those that missed the first part in 2019! ** Required Magic's Carpet: How we designed a mass deployment system for Linux. ** In 2014 we started working with a major Irish bank to help them with a project to upgrade 7,500 Linux workstations across all of their branches. Over the next two years we completed that task - not just once - but on a weekly basis, across 900 locations - with just **two** people, and **zero** site visits. Our discoveries of their systems and techniques led us to build "Carpet" (formally known as "Snoopea"), a tool to rapidly roll out - and maintain - Linux systems across a wide area network. The systems don't have to be desktop based either - so long as the devices are network connected, Carpet can deploy IOT, Server and virtual machines too. This high level talk is an overview of the the journey to take the original CLI based system to a modern, web based tool - including how we used Kiwi (and image builder), and Nuitka (a python compiler) to build certain components. We'll start from the beginning for those that missed the first part in 2019! about this event: https://c3voc.de Thu, 02 Jun 2022 12:30:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3877-eng-As_I_was_saying_sd.mp4?1654539981 BB7wKI00Ff4PLdFjJ1LspA 2022-06-02T12:30:00+02:00 Patrick Fitzgerald No osc22, 3877, 2022, Open Source Using Kiwi-ng in production (Part 2) ** Required Magic's Carpet: How we designed a mass deployment system for Linux. ** In 2014 we started working with a major Irish bank to help them with a project to upgrade 7,500 Linux workstations across all of their branches. Over the next two years we completed that task - not just once - but on a weekly basis, across 900 locations - with just **two** people, and **zero** site visits. Our discoveries of their systems and techniques led us to build "Carpet" (formally known as "Snoopea"), a tool to rapidly roll out - and maintain - Linux systems across a wide area network. The systems don't have to be desktop based either - so long as the devices are network connected, Carpet can deploy IOT, Server and virtual machines too. This high level talk is an overview of the the journey to take the original CLI based system to a modern, web based tool - including how we used Kiwi (and image builder), and Nuitka (a python compiler) to build certain components. We'll start from the beginning for those that missed the first part in 2019! ** Required Magic's Carpet: How we designed a mass deployment system for Linux. ** In 2014 we started working with a major Irish bank to help them with a project to upgrade 7,500 Linux workstations across all of their branches. Over the next two years we completed that task - not just once - but on a weekly basis, across 900 locations - with just **two** people, and **zero** site visits. Our discoveries of their systems and techniques led us to build "Carpet" (formally known as "Snoopea"), a tool to rapidly roll out - and maintain - Linux systems across a wide area network. The systems don't have to be desktop based either - so long as the devices are network connected, Carpet can deploy IOT, Server and virtual machines too. This high level talk is an overview of the the journey to take the original CLI based system to a modern, web based tool - including how we used Kiwi (and image builder), and Nuitka (a python compiler) to build certain components. We'll start from the beginning for those that missed the first part in 2019! about this event: https://c3voc.de 00:36:03 https://media.ccc.de/v/3856-a-better-way-to-make-enlightenment-themes A New Way to Create Enlightenment Themes. Enlightenment Themes are very large and complex, this makes them immensely flexible but also means the amount of effort to create a new Theme is huge. To try and find some middle ground here I have been working on a new theme engine that is much less flexible but means you can create a new theme just by changing images and a couple of files. One of the first examples of this is the new default theme for openSUSE Leap 15.4. In this talk I'll walk through the process of making a new theme with this engine as well as showing a few examples. I'll also show you how to make GTK and KDE apps play nicely together. But because everyone is not interested in Enlightenment i'll spend a fair section of time explaining how gtk and kde themes work and how you can or can't easily make your own versions of them. A New Way to Create Enlightenment Themes. Enlightenment Themes are very large and complex, this makes them immensely flexible but also means the amount of effort to create a new Theme is huge. To try and find some middle ground here I have been working on a new theme engine that is much less flexible but means you can create a new theme just by changing images and a couple of files. One of the first examples of this is the new default theme for openSUSE Leap 15.4. In this talk I'll walk through the process of making a new theme with this engine as well as showing a few examples. I'll also show you how to make GTK and KDE apps play nicely together. But because everyone is not interested in Enlightenment i'll spend a fair section of time explaining how gtk and kde themes work and how you can or can't easily make your own versions of them. about this event: https://c3voc.de Thu, 02 Jun 2022 12:00:00 +0200 https://cdn.media.ccc.de/events/osc/2022/h264-sd/osc22-3856-eng-A_Better_way_to_make_Enlightenment_themes_sd.mp4?1654536886 fjxQOn-hTB9s9DYqOF7wiw 2022-06-02T12:00:00+02:00 Simon Lees No osc22, 3856, 2022, Open Source A New Way to Create Enlightenment Themes. Enlightenment Themes are very large and complex, this makes them immensely flexible but also means the amount of effort to create a new Theme is huge. To try and find some middle ground here I have been working on a new theme engine that is much less flexible but means you can create a new theme just by changing images and a couple of files. One of the first examples of this is the new default theme for openSUSE Leap 15.4. In this talk I'll walk through the process of making a new theme with this engine as well as showing a few examples. I'll also show you how to make GTK and KDE apps play nicely together. But because everyone is not interested in Enlightenment i'll spend a fair section of time explaining how gtk and kde themes work and how you can or can't easily make your own versions of them. A New Way to Create Enlightenment Themes. Enlightenment Themes are very large and complex, this makes them immensely flexible but also means the amount of effort to create a new Theme is huge. To try and find some middle ground here I have been working on a new theme engine that is much less flexible but means you can create a new theme just by changing images and a couple of files. One of the first examples of this is the new default theme for openSUSE Leap 15.4. In this talk I'll walk through the process of making a new theme with this engine as well as showing a few examples. I'll also show you how to make GTK and KDE apps play nicely together. But because everyone is not interested in Enlightenment i'll spend a fair section of time explaining how gtk and kde themes work and how you can or can't easily make your own versions of them. about this event: https://c3voc.de 00:26:20 media.ccc.de / RSS 0.3.1 CCC media team media@c3voc.de CCC media team No CCC Congress Hacking Security Netzpolitik A wide variety of video material distributed by the CCC. All content is taken from cdn.media.ccc.de and media.ccc.de A wide variety of video material distributed by the Chaos Computer Club. This feed contains all events from osc22 as mp4