Chaos Computer Club - recent events feed
Test 2 (entropia)
Oct 2, 20261 min
test 2 @ entropia Licensed to the public under https://creativecommons.org/licenses/by/4.0/ about this event: https://c3voc.de
Loading…
Loading…
technology
Hosted by CCC media team · technology · EN · 1,000 episodes
A wide variety of video material distributed by the Chaos Computer Club. This feed contains events from the last two years
Required Pod Score for this show. PitchCentric checks your profile against host openness, topical fit, and audience signals before you generate a pitch.
Contact path
Verified email
Booking probability
48%
Guest openness
Selective
Sign up to generate a grounded pitch for Chaos Computer Club - recent events feed.
Signup to Generate a PitchChaos Computer Club - recent events feed is a technology podcast hosted by CCC media team, with 1,000 episodes on record and a Required Pod Score of 80.
CCC media team hosts Chaos Computer Club - recent events feed, a technology show with 1,000 episodes published.
Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.
Chaos Computer Club - recent events feed
test 2 @ entropia Licensed to the public under https://creativecommons.org/licenses/by/4.0/ about this event: https://c3voc.de
Chaos Computer Club - recent events feed
When a machine/server/node is serviced and experiences a downtime, that results in a service interruption, customers or users tend to get quite sad. This talk will explore two recent additions to systemd that aim to make these service interruptions as minimal as possible. systemd v260 and v261 added two features which aim to let service owners minimize downtime. Firstly, when services use dm-verity images, profiling data showed that the largest bottleneck by far was loading the new images, which used to happen after the running service had already stopped during a unit restart. Since v260, when very specific conditions are met, this bottleneck has been removed from the critical path. Secondly, a common issue causing slowdowns for services is having to serialize and deserialize large amount of state from slow disks after a reboot due to an OS update. Since v261, systemd supports the kernel's Live Update Orchestration, and uses it to persist the content of the FD Store across a kexec reboot. Services can use a memfd for their runtime state, hand it over the systemd when they are stopped/restarted, and they will get it back and can mmap it and use it straight away on restart. With LUO support, services can rely on this even across a kexec, removing the need to use serialize and deserialize state to disk. This talk will explore both features, explaining how they work and how they can be used. Licensed to the public under https://creativecommons.org/licenses/by/4.0/de/ about this event: https://cfp.all-systems-go.io/all-systems-go-2026/talk/XFZKN8/
Chaos Computer Club - recent events feed
Confidential VM (CVM) instance types are becoming ubiquitous, with all major cloud providers offering them as a key component for achieving “zero trust.” While complete zero trust is currently more of a marketing term than a technical reality, we can acknowledge that CVM technologies help reduce the Trusted Computing Base (TCB) when utilized properly. But do we actually know how to use them effectively? When transitioning from a world of traditional, mutable operating systems, users often expect to gain security benefits simply by moving their existing workloads to new CVM instance types, perhaps with some level of attestation. Unfortunately, in many cases, this looks more like a role play in a “security theater”. Over the past few years, we have investigated what security benefits can truly be unlocked when mutable RHEL or Fedora workloads are deployed on confidential VMs, whether in the public cloud or on-premises. While immutable OSes offer distinct advantages in such scenarios, we pose the question: can traditional (mutable) OSes also benefit? Over the last year, we have contributed several features to systemd (and other components) that we believe can improve the situation. In particular, we are focused on preventing certain attack scenarios against a VM which is normally deployed from a publicly available cloud (marketplace) image. We have further ideas, and in this talk, we will share our vision for how these pieces can fit together. Licensed to the public under https://creativecommons.org/licenses/by/4.0/de/ about this event: https://cfp.all-systems-go.io/all-systems-go-2026/talk/VNXPQS/
Chaos Computer Club - recent events feed
For years, kexec was the standard way to skip lengthy firmware and bootloader delays at reboot. However, in modern cloud environments, even a fast reboot causes severe service degradation. Guests evacuation in virtualized environments or rebuild of massive in-memory caches for large databases is costly and disruptive. Kernel HandOver (KHO) and Live Update Orchestrator (LUO) introduce a complete framework for seamless kernel and userspace state preservation across upgrades. KHO provides the infrastructure to preserve kernel data structures and arbitrary memory regions across kexec. Physically contiguous memory areas managed by KHO let the incoming kernel to bootstrap itself without touching the preserved memory. On top of KHO, LUO provides userspace APIs for coordination of the transition and allows applications to preserve file descriptors across kexec. With initial support for memory file descriptors (memfd), the ecosystem is rapidly expanding to cover subsystems like PCI, VFIO, KVM, guestmemfd, and iommufd. Moreover, the ecosystem now features native systemd integration, leveraging the standard fdstore interface to pass resources across the kernel reboot. Licensed to the public under https://creativecommons.org/licenses/by/4.0/de/ about this event: https://cfp.all-systems-go.io/all-systems-go-2026/talk/J8GNND/
Chaos Computer Club - recent events feed
KDE's new image-based Linux distribution embraces modern technologies whenever possible. We'll explore all the tools that contribute, and how they are being utilized to form the final product. From building the disk image to eventually updating it on the user's system. Licensed to the public under https://creativecommons.org/licenses/by/4.0/de/ about this event: https://cfp.all-systems-go.io/all-systems-go-2026/talk/VXGVJF/
Recent guests on Chaos Computer Club - recent events feed. Study who booked and why before you pitch.
Sponsor detection runs nightly. Check back soon.
Based on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:
Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.
Is this podcast yours and you'd like to remove or correct details? Request removal or email privacy@pitchcentric.com.
FAQs
If you have a concern about deliverability, AI quality, data privacy, or whether this will actually work for your specific situation, it's probably answered below.
Founder Solo gives you 50 AI pitches per month using the credit model (Standard pitches cost 1 credit, Enriched pitches cost 2). Founder Pro raises that to 200 credits per month and adds full Booking Probability access, unlimited Magic Match, Apollo enrichment credits, and data export capabilities. Both plans use the same credit system, so you can stretch your monthly budget further by using Standard-mode drafting.
Agency tiers have no base fee. You pay per managed client and per talent profile. Agency Standard is $199 per client per month; Agency Pro is $399 per client per month. Both add $39 per talent profile per month. Your own team's user seats are always free.
A talent profile represents one person (founder, executive, or spokesperson) you are booking onto podcasts. It includes their bio, topics, headshots, and outreach history. Team plans include 5 profiles; agency plans are pay-as-you-go.
Yes, at any time. Upgrades take effect immediately; downgrades apply at the end of the current billing period. Contact support if you need help migrating between plan families.
Every paid plan includes a 15-day free trial. Your card is saved at signup but you will not be charged until day 16. Cancel any time from your dashboard.
You keep access until the end of your current billing period. No charges after that. Your data is retained for 30 days in case you reactivate.
Yes. Select Annual on the pricing toggle and the discounted price is applied automatically at checkout. The annual price shown is the full year cost.
That is our Enterprise tier. Contact our sales team and we will build a custom plan with volume pricing, a dedicated account manager, and SLA guarantees.
