update changelog, version numbers, and regenerate docs

Author: squell

CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## [0.2.15] - 2026-08-31
+
+### Added
+- `Defaults !log_allowed` to suppress writing successful command invocations
+  to the system log. (#1181)
+- `Defaults timestamp_type=ppid` to allow tightly binding cached credentials
+  to the parent process even if a TTY is present. (#1621)
+
+### Changed
+- Allow authenticating users that have an empty password set (#1656)
+- Environment variables supplied on the command line are now ignored instead
+  of resulting in an error message when used with `-v`, `-k` or `-K` (#1578)
+
+### Fixed
+- sudo used in pipe such as `sudo cmd1 | sudo cmd2` could result in a fight for
+  control over the TTY used for password input (#1650)
+- Groups loaded dynamically (for example by `pam_groups.so`) were not used for
+  policy judgments (#1660)
+- Fixed the error message when `sudo -g` was used with an invalid group (#1628)
+- No longer emit a newline after password entry if `-p ''` is used (#1648)
+- Tabs were not recognized as argument separators in /etc/sudoers (#1669)
+- `sudoedit /path/to/file` restrictions in `/etc/sudoers` could be circumvented
+  by causing a symlink race (GHSA-f42v-x7gq-phc8)
+
 ## [0.2.14] - 2026-06-23
 
 ### Added

Cargo.lock

@@ -1,7 +1,7 @@
 [package]
 name = "sudo-rs"
 description = "A memory safe implementation of sudo and su."
-version = "0.2.14"
+version = "0.2.15"
 license = "Apache-2.0 OR MIT"
 edition = "2024"
 repository = "https://github.com/trifectatechfoundation/sudo-rs"

Cargo.toml

@@ -138,13 +138,13 @@ We recommend installing sudo-rs and su-rs in your `/usr/local` hierarchy so it d
 manager of your Linux distribution. You can achieve this using the commands:
 
 ```sh
-sudo tar -C /usr/local -xvf sudo-0.2.14.tar.gz
+sudo tar -C /usr/local -xvf sudo-0.2.15.tar.gz
 ```
 
 and for su-rs:
 
 ```sh
-sudo tar -C /usr/local -xvf su-0.2.14.tar.gz
+sudo tar -C /usr/local -xvf su-0.2.15.tar.gz
 ```
 
 This will install sudo-rs and su-rs in `/usr/local/bin` using the usual commands `sudo`, `visudo`, `sudoedit` and `su`. Please double check

README.md

@@ -1,6 +1,6 @@
 .\" Automatically generated by Pandoc 3.6.3
 .\"
-.TH "SU" "1" "" "sudo\-rs 0.2.14" "sudo\-rs"
+.TH "SU" "1" "" "sudo\-rs 0.2.15" "sudo\-rs"
 .SH NAME
 \f[CR]su\f[R] \- run a shell or command as another user
 .SH SYNOPSIS

docs/man/su.1.man

@@ -1,5 +1,5 @@
 ---
-title: SU(1) sudo-rs 0.2.14 | sudo-rs
+title: SU(1) sudo-rs 0.2.15 | sudo-rs
 ---
 
 # NAME

docs/man/su.1.md

@@ -1,6 +1,6 @@
 .\" Automatically generated by Pandoc 3.6.3
 .\"
-.TH "SUDO" "8" "" "sudo\-rs 0.2.14" "sudo\-rs"
+.TH "SUDO" "8" "" "sudo\-rs 0.2.15" "sudo\-rs"
 .SH NAME
 \f[CR]sudo\f[R], \f[CR]sudoedit\f[R] \- execute a command as another
 user

docs/man/sudo.8.man

@@ -1,5 +1,5 @@
 ---
-title: SUDO(8) sudo-rs 0.2.14 | sudo-rs
+title: SUDO(8) sudo-rs 0.2.15 | sudo-rs
 ---
 
 # NAME

docs/man/sudo.8.md

@@ -1,6 +1,6 @@
 .\" Automatically generated by Pandoc 3.6.3
 .\"
-.TH "SUDOERS" "5" "" "sudo\-rs 0.2.14" "sudo\-rs"
+.TH "SUDOERS" "5" "" "sudo\-rs 0.2.15" "sudo\-rs"
 .SH NAME
 \f[CR]sudoers\f[R] \- sudo\-compatible security configuration
 .SH DESCRIPTION
@@ -671,7 +671,7 @@ also present in a different file.
 When managing enterprise\-wide sudoers rules, it is sometimes preferable
 to store them in a centralized repository.
 The \[at]socket directive can be used to include the contents provided
-by a server application over a unix domain socket.
+by a server application over a Unix domain socket.
 For example, providing:
 .IP
 .EX
@@ -686,16 +686,19 @@ There is, however, one exception: when reading from a socket, the
 accepted.
 .PP
 For security reasons, a user and optionally a group must be given,
-enclosed in parentheses and separated by a colon. Users and groups can
-be specified either by their name or by their numeric id preceded by a
-hash sign (#). When the socket is opened, and before any interaction with
-it, sudo will check that the peer process at the other side of the socket
-runs as the declared user and group (if the latter was provided). If any
-of these conditions fail, the socket is immediately closed and discarded.
+enclosed in parentheses and separated by a colon.
+Users and groups can be specified either by their name or by their
+numeric id preceded by a hash sign (#).
+When the socket is opened, and before any interaction with it, sudo will
+check that the peer process at the other side of the socket runs as the
+declared user and group (if the latter was provided).
+If any of these conditions fail, the socket is immediately closed and
+discarded.
 Only POSIX groups can be used.
 .PP
-Please note that visudo cannot read from a socket. Furthermore, the
-contents retrieved from a socket are considered immutable by sudo.
+Please note that visudo cannot read from a socket.
+Furthermore, the contents retrieved from a socket are considered
+immutable by sudo.
 .SS Other special characters and reserved words
 The pound sign (`#') is used to indicate a comment (unless it is part of
 a #include directive or unless it occurs in the context of a user name
@@ -749,6 +752,14 @@ A list of all supported Defaults parameters, grouped by type, are listed
 below.
 .SS Boolean Flags:
 .IP \[bu] 2
+log_allowed
+.RS 2
+.PP
+If set, sudoers will log commands allowed by the policy to the system
+log.
+This flag is on by default.
+.RE
+.IP \[bu] 2
 noexec
 .RS 2
 .PP
@@ -759,15 +770,19 @@ shell escapes\f[R] section at the end of this manual.
 This flag is off by default.
 .RE
 .IP \[bu] 2
-noninteractive_auth If set, authentication will be attempted even in
-non\-interactive mode (when sudo\[cq]s \-n option is specified).
+noninteractive_auth
+.RS 2
+.PP
+If set, authentication will be attempted even in non\-interactive mode
+(when sudo\[cq]s \-n option is specified).
 This allows authentication methods that don\[cq]t require user
 interaction to succeed.
 Authentication methods that require input from the user\[cq]s terminal
 will still fail.
 If disabled, authentication will not be attempted in non\-interactive
 mode.
 This flag is off by default.
+.RE
 .IP \[bu] 2
 env_editor
 .RS 2
@@ -917,6 +932,32 @@ The default on Linux is
 \f[I]/usr/bin/editor:/usr/bin/nano:/usr/bin/vi\f[R].
 On FreeBSD the default is \f[I]/usr/bin/vi\f[R].
 .RE
+.IP \[bu] 2
+timestamp_type
+.RS 2
+.PP
+sudo\-rs uses per\-user timestamp files for credential caching.
+The \f[I]timestamp_type\f[R] option can be used to specify the type of
+timestamp record used.
+It has two possible values: \f[I]tty\f[R] and \f[I]ppid\f[R].
+There is no support for a \f[I]global\f[R] or \f[I]kernel\f[R] setting.
+.IP \[bu] 2
+\f[I]ppid\f[R]: A single timestamp record is used for all processes with
+the same parent process ID (usually the shell).
+Commands run from the same shell (or other common parent process) will
+not require a password while the timestamp is valid (see
+\f[I]timestamp_timeout\f[R]).
+Commands run via sudo with a different parent process ID, for example
+from a shell script, must be authenticated separately.
+.IP \[bu] 2
+\f[I]tty\f[R]: One timestamp record is used for each terminal, which
+means that a user\[cq]s login sessions are authenticated separately.
+If no terminal is present, the behavior is the same as \f[I]ppid\f[R].
+Commands run from the same terminal will not require a password while
+the timestamp is valid.
+.PP
+The default value is \f[B]tty\f[R].
+.RE
 .SS Strings that can be used in a boolean context:
 .IP \[bu] 2
 apparmor_profile

docs/man/sudoers.5.man

@@ -1,5 +1,5 @@
 ---
-title: SUDOERS(5) sudo-rs 0.2.14 | sudo-rs
+title: SUDOERS(5) sudo-rs 0.2.15 | sudo-rs
 ---
 
 # NAME