Ubuntu 26.04 Switched to sudo-rs: Why Some /etc/sudoers.d Rules Stop WorkingBrief · digest for November 22
Brief≈ 2 min

Ubuntu 26.04 Switched to sudo-rs: Why Some /etc/sudoers.d Rules Stop Working

You upgrade a server to Ubuntu 26.04 LTS, run your usual Ansible deploy, and a task fails without leaving a single line in the logs. The culprit is sudo-rs—a Rust rewrite of sudo by Trifecta Tech Foundation that is now the default and drops several legacy features from classic C sudo.

The breakage hits /etc/sudoers.d, the folder holding drop-in permission files for running commands as root. sudo-rs rejects * wildcards inside arguments like /bin/rm -f /etc/cron.d/app-* (wildcards are only allowed at the end of a command path). It also drops legacy Defaults such as requiretty, authenticate (including Defaults !authenticate), log_output, and logfile, causing the parser to complain about unknown settings.

After upgrading, check which version is active and run your configs through visudo—the built-in sudo syntax validator, which checks rules with -c without opening an editor:

# Check which sudo implementation is active
sudo --version | head -1

# Validate /etc/sudoers and /etc/sudoers.d/
sudo visudo -c

# Roll back to classic sudo.ws if playbooks break
sudo apt install sudo
sudo update-alternatives --set sudo /usr/bin/sudo.ws

If visudo -c stays quiet, you're safe to stick with sudo-rs. And if you don't have time to rewrite old playbooks right now, the two update-alternatives commands above restore classic /usr/bin/sudo.ws without rolling back the whole OS.

Want a deep diveVotes help us choose what to break down in detail. This material has 0 votes.
Sources · 3