# canonical Published articles for canonical. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Ubuntu Noble's likely last point release lands, then loses its desktop download DevFeed: [Ubuntu Noble's likely last point release lands, then loses its desktop download]() Original publisher: [Read original article]() Author: Liam Proven Published: 2026-09-14T16:45:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [Ubuntu](), [bug]() Tags: [bug](), [canonical](), [desktop](), [download](), [os-platforms](), [release](), [software-bug](), [ubuntu]() ### AI overview Ubuntu Noble's likely final point release has landed, but its desktop download is being withdrawn. An installer bug crashes extended setups as the next Ubuntu release approaches its October debut. ### Source excerpt Installer bug crashes extended setups while Stonking Stingray circles ahead of October debut ## Ubuntu Developers Contemplate Linux Firmware HWE Package DevFeed: [Ubuntu Developers Contemplate Linux Firmware HWE Package]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-12T10:25:11Z Content type: news Language: en Sources: [Phoronix]() Topics: [Ubuntu](), [Linux](), [Hardware](), [releases]() Tags: [amd](), [canonical](), [desktop-linux](), [developers](), [enablement](), [firmware](), [hardware](), [kernel](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [lts](), [open-source-graphics](), [packages](), [phoronix](), [phoronix-test-suite](), [ubuntu](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview Ubuntu developers are considering a linux-firmware-hwe package tied to Hardware Enablement kernels on Ubuntu LTS releases. The proposal aims to align firmware with newer HWE kernels while reducing regressions for systems using the original GA kernels. ### Source excerpt A possible future enhancement being considered for Ubuntu Long Term Support "LTS" releases is the introduction of a linux-firmware-hwe package as part of their hardware enablement (HWE) stack... ## Supporter spotlight: Kees Cook on Linux kernel security DevFeed: [Supporter spotlight: Kees Cook on Linux kernel security]() Original publisher: [Read original article]() Published: 2024-09-29T00:00:00Z Content type: article Language: en Sources: [reproducible-builds.org]() Topics: [Linux Kernel](), [Security](), [open-source-security](), [free software](), [Arm](), [Ubuntu](), [Debian](), [Fedora]() Tags: [arm](), [canonical](), [debian](), [fedora](), [free-software](), [kernel](), [linux](), [linux-kernel](), [open-source-security](), [org](), [security](), [ubuntu]() ### AI overview This supporter spotlight interviews Kees Cook, founder of the Kernel Self-Protection Project, about his work improving Linux kernel security. He discusses kernel self-protection, recruiting expertise in ARM and memory management, and his earlier security-hardening work at Canonical on Ubuntu. ### Source excerpt The Reproducible Builds project relies on several projects, supporters and sponsors for financial support, but they are also valued as ambassadors who spread the word about our project and the work that we do. This is the eighth installment in a series featuring the projects, companies and individuals who support the Reproducible Builds project. We started this series by featuring the Civil Infrastructure Platform project, and followed this up with a post about the Ford Foundation as well as recent ones about ARDC, the Google Open Source Security Team (GOSST), Bootstrappable Builds, the F-Droid project, David A. Wheeler and Simon Butler. Today, however, we will be talking with Kees Cook, founder of the Kernel Self-Protection Project. Vagrant Cascadian: Could you tell me a bit about yourself? What sort of things do you work on? Kees Cook: I'm a Free Software junkie living in Portland, Oregon, USA. I have been focusing on the upstream Linux kernel's protection of itself. There is a lot of support that the kernel provides userspace to defend itself, but when I first started focusing on this there was not as much attention given to the kernel protecting itself. As userspace got more hardened the kernel itself became a bigger target. Almost 9 years ago I formally announced the Kernel Self-Protection Project because the work necessary was way more than my time and expertise could do alone. So I just try to get people to help as much as possible; people who understand the ARM architecture, people who understand the memory management subsystem to help, people who understand how to make the kernel less buggy. Vagrant: Could you describe the path that lead you to working on this sort of thing? Kees: I have always been interested in security through the aspect of exploitable flaws. I always thought it was like a magic trick to make a computer do something that it was very much not designed to do and seeing how easy it is to subvert bugs. I wanted to improve that fragility. In ## Hardened Container Images: Images for a Secure Supply Chain DevFeed: [Hardened Container Images: Images for a Secure Supply Chain]() Original publisher: [Read original article]() Published: 2024-04-30T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [supply-chain-security](), [chainguard images](), [Containers](), [container-security](), [Vulnerabilities](), [grype](), [snyk]() Tags: [canonical](), [canonical-chiselled-image](), [chainguard](), [chainguard-images](), [container](), [container-image](), [container-images](), [container-security](), [containers](), [cve](), [debian](), [dockerhub](), [false-positives](), [grype](), [hardened-container-image](), [iron-bank](), [redhat](), [scanners](), [security](), [shift-left](), [snyk](), [software-supply-chain](), [supply-chain](), [vulnerabilities]() ### AI overview Chainguard introduces its inaugural State of Hardened Container Images report, examining the security of hardened container images from providers including Red Hat, Iron Bank, and Chainguard. The article argues that hardened container images deserve distinct consideration from container vulnerability scanning and describes the report as addressing secure software supply chains. ### Source excerpt Check out our analysis of the hardened container image landscape, including offerings from Red Hat, Iron Bank, and others. ## Deploying Machines with MaaS and Packer - Metal as a Service + Hashicorp Packer Tutorial DevFeed: [Deploying Machines with MaaS and Packer - Metal as a Service + Hashicorp Packer Tutorial]() Original publisher: [Read original article]() Author: Techno Tim Published: 2023-01-28T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Tutorial](), [canonical](), [systems](), [Cloud](), [Linux](), [Windows](), [virtual machines](), [Oracle-VM-VirtualBox]() Tags: [boot](), [canonical](), [cloud](), [dhcp](), [hashicorp](), [how-to](), [linux](), [maas](), [networking](), [operating-systems](), [systems](), [tutorial](), [ubuntu](), [virtual-machines](), [windows]() ### AI overview A tutorial on installing and configuring Canonical MaaS to provision bare-metal and virtual machines, deploy operating systems, configure networking and network boot, commission machines, and create and upload custom images with Hashicorp Packer. ### Source excerpt MaaS or Metal as a service from Canonical is a great way to provision bare metal machines as well as virtual machines.MaaS allows you to deploy Windows, Linux, ESXi, and many other operating systems to your systems helping you to build a bare metal cloud.You can even use Packer from Hashicorp to configure custom images too! We'll cover all of this and more in this tutorial on how to install an... ## Forge: Ubuntu 22.04 Support DevFeed: [Forge: Ubuntu 22.04 Support]() Original publisher: [Read original article]() Author: James Brooks Published: 2022-05-10T14:16:00Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [Ubuntu](), [Laravel](), [Server](), [PHP](), [MySQL](), [Redis]() Tags: [canonical](), [laravel](), [lts](), [mysql](), [php](), [redis](), [release](), [ubuntu]() ### AI overview Laravel Forge now supports provisioning servers with Ubuntu 22.04, while continuing to support Ubuntu 20.04 LTS. Ubuntu 22.04 includes OpenSSL 3.0 and therefore requires PHP 8.1; older PHP versions require Ubuntu 20.04. Forge can manage PHP servers with services including MySQL and Redis. ### Source excerpt We're excited to announce that Laravel Forge now supports Ubuntu 22.04 (Jammy) - the latest Ubuntu LTS release from Canonical! ## Introducing Contracts: serve many audiences with a unified graph DevFeed: [Introducing Contracts: serve many audiences with a unified graph]() Original publisher: [Read original article]() Author: Vivek Ravishankar Published: 2021-11-10T10:45:05Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [Graphs](), [Binance](), [Authorization](), [Front end](), [Back end]() Tags: [access-control](), [announcement](), [apis](), [apollo-federation](), [canonical](), [feature](), [modularity]() ### AI overview Apollo introduces Contracts, a preview feature on its Enterprise plan that creates tailored contract graphs by filtering a single unified graph for different audiences. The feature aims to preserve unified-graph benefits while supporting audience-specific schemas, access levels, and experiences. ### Source excerpt At Apollo, we talk a lot about building a unified graph, and for good reason. A unified graph provides incredible benefits - a single source of truth for all services, faster apps, faster delivery, less maintenance overhead, and more. But unification introduces new challenges, especially at scale; "How do I support different experiences and levels of access for different personas or types of users like customers, employees, suppliers, and partners?" "How do I provide my partners and public API... ## The road to the Mobian Community Edition (part 1) DevFeed: [The road to the Mobian Community Edition (part 1)]() Original publisher: [Read original article]() Author: Mobian team Published: 2021-04-08T00:00:00Z Content type: article Language: en Sources: [Mobian's Blog]() Topics: [Development](), [Mobile](), [Linux](), [Operating system](), [touchscreen](), [Ubuntu](), [USB]() Tags: [android](), [canonical](), [community](), [development](), [hacking](), [kernel](), [linux](), [mobile](), [touchscreen](), [usb]() ### AI overview This article recounts the early development of the Mobian project, a Linux-based mobile operating system, and the path toward the Mobian Community Edition for PinePhone. It describes the author's initial PinePhone experimentation, the available mobile Linux ecosystem, and the project's early software limitations. ### Source excerpt The Mobian project was officially announced on May 14th, 2020. But those who witnessed its birth surely remember it all started a few months prior to this date, a bit more than one year ago, actually. One year hacking and building both a mobile operating system and a community. One year refining our system, getting rid of the early days' hacks in favor of more mature and robust solutions. One year ending with a major milestone for such a young project: getting the Mobian Community Edition PinePhone into the hands of thousands of users. One hell of a year, indeed! It all really started on January 29th, 2020, when I received a shiny new toy: an ARM64 development system packed with a number of interesting, if not unique, features: 5.95" touchscreen removable battery integrated eMMC µSD socket USB-C port 3.5" headset jack 4G modem The PinePhone was my first "real" Linux phone: I had owned a Nexus 5 running Ubuntu Touch, but it was basically an Android phone, running an Android kernel. While it was a very fine device, definitely usable as a daily driver, I got quickly frustrated by all the things I couldn't do on this system, mostly due to Canonical's design choices: it was not a hacker's device, just a different, yet mainstream, mobile phone. Let's be honest, back when PINE64 announced the PinePhone, I had already pre-ordered a Librem 5, and I only purchased this device so I could play with Phosh and the L5 software stack while waiting for my "real" phone. But still, there was literally a world to build with the PinePhone, so why not give it a try? Unboxing and early hacking While waiting on the PinePhone, I gathered as much documentation as possible about the device itself, but also the existing ecosystem: select developers had access to an even earlier version of this phone, and there were already a few systems available. Among those, postmarketOS looked the most promising, as it allowed the user to chose various environments, Plasma Mobile and Phosh being the ones I ## The 1.x Files: A Primer for the Witness Specification DevFeed: [The 1.x Files: A Primer for the Witness Specification]() Original publisher: [Read original article]() Author: Griffin Ichiba Hotchkiss Published: 2020-05-04T00:00:00Z Content type: tutorial Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Blockchain](), [Data structures](), [Code]() Tags: [blockchain](), [canonical](), [consensus](), [data-structure](), [ethereum](), [hashing](), [research-development]() ### AI overview This primer explains the formal Witness Specification as part of the Stateless Ethereum effort. It introduces Ethereum state, including accounts, balances, smart-contract code and memory, and describes how the state is represented by a Merkle-Patricia Trie whose root hash can be used for verification. ### Source excerpt Since a lot of us have a bit more time on our hands, I thought now might be a good opportunity to proceed with something perhaps a little bit boring and tedious, but nevertheless quite fundamental to the Stateless Ethereum effort: understanding the formal Witness Specification. Like the captain...