The sudo 1.8 branch is considered the legacy version. It receives no new features, only critical bug fixes. Users are highly encouraged to migrate to the sudo stable branch. The current legacy release of sudo is 1.8.32. For full details see the ChangeLog file or view the commit history via git or GitHub. Sudo 1.8.32 Fixed a regression introduced in sudo 1.8.9 where the closefrom sudoers option could not be set to a value of 3. Bug #950.| Sudo
2024-04-19 Todd C. Miller plugins/sudoers/cvtsudoers_json.c, plugins/sudoers/regress/sudoers/test24.json.ok: When converting CWD and CHROOT tags, store them as objects. Fixes GitHub issue #369 [bf7c37a8477c] [tip] 2024-04-17 Todd C. Miller docs/sudoers.man.in, docs/sudoers.mdoc.in, plugins/sudoers/auth/pam.c, plugins/sudoers/def_data.c, plugins/sudoers/def_data.h, plugins/sudoers/def_data.in, plugins/sudoers/defaults.c: Add pam_silent sudoers option. Inspired by PR #368 GitHub issue #216 [767...| Releases on Sudo
The current stable release of the sudo 1.9 branch is version 1.9.16p2. For the sudo 1.8 branch, see legacy releases. For full details see the ChangeLog file or view the commit history via git or GitHub. Sudo 1.9.16p2 Sudo now passes the terminal device number to the policy plugin even if it cannot resolve it to a path name. This allows sudo to run without warnings in a chroot jail when the terminal device files are not present. GitHub issue #421.| Sudo
The current development release of sudo is 1.9.16rc2. Binary packages are also available for development releases. For full details see the ChangeLog file or view the commit history via git or GitHub. If you plan to use a development release of sudo, please subscribe to the sudo-workers mailing list so that you will receive updates on bug fixes and related announcements. You may also be interested in the sudo-commits mailing list which receives a message for each commit to the sudo source tree.| Sudo