Raspberry Pi OS 6.2 Disables Passwordless Sudo by Default, Drops PulseAudio for PipeWire in Biggest Desktop Overhaul Since Trixie Migration
Raspberry Pi OS 6.2 tightens security by requiring a password for sudo commands on new installations and replaces PulseAudio with PipeWire across the desktop stack.
Overview
Raspberry Pi OS 6.2, released on April 14, has disabled passwordless sudo by default on all new installations, closing a long-standing security gap that gave any local user unrestricted administrator access without authentication. The release, based on Debian Trixie and running the Linux 6.12.75 LTS kernel, also replaces PulseAudio with PipeWire for audio, overhauls the desktop menu system, and bundles uBlock Origin Lite in Chromium out of the box.
The changes mark the most significant update to the Raspberry Pi desktop experience since the operating system migrated to the Trixie base earlier this year.
The Sudo Change
Since its inception, Raspberry Pi OS shipped with passwordless sudo enabled by default, meaning any user could execute administrator-level commands without any authentication challenge. As Simon Long, Senior Principal Software Engineer at Raspberry Pi, wrote in the official announcement, “anyone who can access the computer can perform administrator actions from a regular user account, some of which could be malicious.”
With version 6.2, new installations now prompt for the current user’s password whenever a sudo command is issued, whether in the terminal or through the desktop interface. Once a correct password is entered, the system caches the credential for five minutes, according to Raspberry Pi, so consecutive administrative commands remain frictionless.
The change does not affect existing installations. Users who update from an older version will see a new “Admin Password” toggle in Control Centre’s System tab, but passwordless sudo will remain enabled unless they actively switch it on, as noted in the official blog post. Those who prefer the old behavior on fresh installations can disable the requirement through Control Centre or raspi-config.
What We Know
-
PulseAudio removed: Raspberry Pi OS 6.2 drops PulseAudio entirely, replacing it with direct PipeWire audio control integrated into the first-boot wizard, according to Linuxiac. This aligns Raspberry Pi OS with the broader Linux desktop trend toward PipeWire, which has already become the default in Fedora, Ubuntu, and most major distributions.
-
New menu system: The release replaces Alacarte, the traditional GNOME menu editor, with a new Main Menu tab built into Control Centre. Applications now use standard
gtk-launchcode, according to Linuxiac. -
Browser hardening: Chromium now ships with uBlock Origin Lite and h264ify installed by default, along with
libpam-gnome-keyringfor password management, as reported by Linuxiac. -
Printer service changes: The
cups-browseddaemon no longer runs continuously in the background and is instead controlled through Control Centre, per Linuxiac. -
Taskbar improvements: New launcher and task list plugins support drag-and-drop reordering, according to Linuxiac.
What We Don’t Know
Raspberry Pi has not disclosed how many active installations are running Raspberry Pi OS or how many users are expected to adopt the new defaults. The Foundation acknowledged the tension inherent in the change: “anything that makes the operating system more secure will invariably inconvenience legitimate users,” as The Register reported. Community reaction has been mixed, with some users welcoming the security improvement and others calling it an unnecessary friction for devices that are often used headlessly or in controlled environments.
It also remains to be seen whether the Foundation will eventually enforce the password requirement on existing installations through a future update, or whether the opt-in approach will persist indefinitely.
Analysis
The passwordless sudo default was a deliberate design choice from Raspberry Pi’s earliest days, when the platform was primarily an educational tool used in classrooms and hobby projects where ease of use took priority over hardening. As the ecosystem matured and Raspberry Pi boards became fixtures in home servers, IoT gateways, and industrial edge deployments, the default became an increasingly conspicuous outlier among Linux distributions.
By aligning with the standard Linux convention of requiring password authentication for elevated privileges, Raspberry Pi OS reduces the attack surface for any device that is network-accessible or shared among multiple users. The five-minute credential cache strikes a reasonable middle ground, preserving workflow continuity while closing the widest door.