Life Behind the Tinfoil: A Look at Qubes and Copperhead
summary
Daily use report: QubesOS runs as a full daily workstation for years but demands 24 GB RAM (8+ will be painful), NVMe SSD, VT-x+VT-d CPU and many cores; it isolates apps with Xen-based disposable VMs, a dedicated USB VM and per-VM network gateways, and uses template VMs — copy/paste and launch lag, suspend/resume bugs and manual backups are frequent annoyances. CopperheadOS is a hardened AOSP on Pixel devices with better battery and fast patches but lost signing keys break OTA updates, many Play-dependent apps and notifications fail, and maintaining updates is manual.
AI-written summary · about
chapters (14)
- 0:00Start
- 6:02Os Guiding Principles
- 11:34What's the Installation like
- 14:28Templates
- 15:04Community Templates
- 18:45Config Global Configuration Files
- 20:32Upgrades
- 22:35Launch Lag
- 24:26The Future Outlook for Cubes Os
- 26:01Who Is It for
- 32:46Copperhead Os
- 33:35What Are the Guiding Principles behind Copperhead
- 35:22Device Requirements
- 39:41They Know Where You Are They Know What You'Re Doing There's You Know Still Being Tracked through the Browsers All that Stuff so There Is Caveat Emptor There so Your Mobile Service Provider Still Checks You There's Fast Security Patches That Come to Your Pure Asp Device Main Lineage Os Is Great at this Copperhead Os Is Also Very Great at It They Patch the Bluetooth Vulnerability within Literally Six Hours of It Becoming Available There's Knowledge that You'Re Using Free Software so F-Droid Supports Reproducible Build so that's Cool Stuff
related talks
22mQubes OS
32mQubes OS: Security Through Isolation
24mThe future of the desktop is on hypervisor powered containers
21mUsing a cloud to manage a cloud
25mOne Size Fits None: Lightweight Workload-Specialized Confidential Containers
41mSecuring Your Xen-Based Cloud
44mAdvancements in Confidential Computing
21mOak stage0: a minimal firmware for (confidential) virtual machines