Bug 272255 - [PATCH] security/sudo: Update to 1.9.14
Summary: [PATCH] security/sudo: Update to 1.9.14
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Renato Botelho
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-27 22:48 UTC by Cy Schubert
Modified: 2023-06-29 13:34 UTC (History)
0 users

See Also:
garga: maintainer-feedback+


Attachments
Update sudo to 19.14 (1.08 KB, patch)
2023-06-27 22:48 UTC, Cy Schubert
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Cy Schubert freebsd_committer freebsd_triage 2023-06-27 22:48:12 UTC
Created attachment 243046 [details]
Update sudo to 19.14

Sudo version 1.9.14 is now available.  In addition to bug fixes, a
major change in version 1.9.14 is that commands are now run their
own pseudo-terminal by default.  To restore the historic default
behavior where commands are run in the user's terminal, add:

    Defaults !use_pty

to your sudoers file.

Source:
    https://www.sudo.ws/dist/sudo-1.9.14.tar.gz
    ftp://ftp.sudo.ws/pub/sudo/sudo-1.9.14.tar.gz

SHA256 checksum:
    7bb70e4529ab2ada47ded970cdf2fe7be3084912861ddbac239eebdc92935a29
MD5 checksum:
    f73b7b18fafceecbd5d3ac4462f09871

Binary packages:
    https://www.sudo.ws/getting/packages/
    https://github.com/sudo-project/sudo/releases/tag/SUDO_1_9_14

For a list of download mirror sites, see:
    https://www.sudo.ws/getting/download_mirrors/

Sudo web site:
    https://www.sudo.ws/

Major changes between sudo 1.9.14 and 1.9.13p3:

 * Fixed a bug where if the "intercept" or "log_subcmds" sudoers
   option was enabled and a sub-command was run where the first
   entry of the argument vector didn't match the command being run.
   This resulted in commands like "sudo su -" being killed due to
   the mismatch.  Bug #1050.

 * The sudoers plugin now canonicalizes command path names before
   matching (where possible).  This fixes a bug where sudo could
   execute the wrong path if there are multiple symbolic links with
   the same target and the same base name in sudoers that a user is
   allowed to run.  GitHub issue #228.

 * Improved command matching when a chroot is specified in sudoers.
   The sudoers plugin will now change the root directory id needed
   before performing command matching.  Previously, the root directory
   was simply prepended to the path that was being processed.

 * When NETGROUP_BASE is set in the ldap.conf file, sudo will now
   perform its own netgroup lookups of the host name instead of
   using the system innetgr(3) function.  This guarantees that user
   and host netgroup lookups are performed using  the same LDAP
   server (or servers).

 * Fixed a bug introduced in sudo 1.9.13 that resulted in a missing
   " ; " separator between environment variables and the command
   in log entries.

 * The visudo utility now displays a warning when it ignores a file
   in an include dir such as /etc/sudoers.d.

 * When running a command in a pseudo-terminal, sudo will initialize
   the terminal settings even if it is the background process.
   Previously, sudo only initialized the pseudo-terminal when running
   in the foreground.  This fixes an issue where a program that
   checks the window size would read the wrong value when sudo was
   running in the background.

 * Fixed a bug where only the first two digits of the TSID field
   being was logged.  Bug #1046.

 * The "log_pty" sudoers option is now enabled by default.  To
   restore the historic behavior where a command is run in the
   user's terminal, add "Defaults !use_pty" to the sudoers file.
   GitHub issue #258.

 * Sudo's "-b" option now works when the command is run in a
   pseudo-terminal.

 * When disabling core dumps, sudo now only modifies the soft limit
   and leaves the hard limit as-is.  This avoids problems on Linux
   when sudo does not have CAP_SYS_RESOURCE, which may be the case
   when run inside a container.  GitHub issue #42.

 * Sudo configuration file paths have been converted to colon-separated
   lists of paths.  This makes it possible to have configuration
   files on a read-only file system while still allowing for local
   modifications in a different (writable) directory.  The new
   --enable-adminconf configure option can be used to specify a
   directory that is searched for configuration files in preference
   to the sysconfdir (which is usually /etc).

 * The "intercept_verify" sudoers option is now only applied when
   the "intercept" option is set in sudoers.  Previously, it was
   also applied when "log_subcmds" was enabled.

 * The NETGROUP_QUERY ldap.conf parameter can now be disabled for
   LDAP servers that do not support querying the nisNetgroup object
   by its nisNetgroupTriple attribute, while still allowing sudo to
   query the LDAP server directly to determine netgroup membership.

 * Fixed a long-standing bug where a sudoers rule without an explicit
   runas list allowed the user to run a command as root and any
   group instead of just one of the groups that root is a member
   of.  For example, a rule such as "myuser ALL = ALL" would permit
   "sudo -u root -g othergroup" even if root did not belong to
   "othergroup".

 * Fixed a bug where a sudoers rule with an explicit runas list
   allowed a user to run sudo commands as themselves.  For example,
   a rule such as "myuser ALL = (root) ALL", "myuser" should only
   allow commands to be run as root (optionally using one of root's
   groups).  However, the rule also allowed the user to run
   "sudo -u myuser -g myuser command".

 * Fixed a bug that prevented the user from specifying a group on
   the command line via "sudo -g" if the rule's Runas_Spec contained
   a Runas_Alias.

 * Sudo now requires a C compiler that conforms to ISO C99 or higher
   to build.
Comment 1 Renato Botelho freebsd_committer freebsd_triage 2023-06-28 11:02:45 UTC
Approved.  Thanks!
Comment 2 commit-hook freebsd_committer freebsd_triage 2023-06-29 13:30:03 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=20ef9f749e3b6add565b2c3a1518771f5ad50f77

commit 20ef9f749e3b6add565b2c3a1518771f5ad50f77
Author:     Cy Schubert <cy@FreeBSD.org>
AuthorDate: 2023-06-27 22:46:32 +0000
Commit:     Cy Schubert <cy@FreeBSD.org>
CommitDate: 2023-06-29 13:28:55 +0000

    security/sudo: Update to 1.9.14

    PR:             272255
    Approved by:    garga (maintainer)
    MFH"            2023Q2

 security/sudo/Makefile | 2 +-
 security/sudo/distinfo | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)
Comment 3 commit-hook freebsd_committer freebsd_triage 2023-06-29 13:33:04 UTC
A commit in branch 2023Q2 references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=1faa491d81afd8b5e26c56b3ca59bcf5b2c512a8

commit 1faa491d81afd8b5e26c56b3ca59bcf5b2c512a8
Author:     Cy Schubert <cy@FreeBSD.org>
AuthorDate: 2023-06-27 22:46:32 +0000
Commit:     Cy Schubert <cy@FreeBSD.org>
CommitDate: 2023-06-29 13:32:04 +0000

    security/sudo: Update to 1.9.14

    PR:             272255
    Approved by:    garga (maintainer)

    (cherry picked from commit 20ef9f749e3b6add565b2c3a1518771f5ad50f77)

 security/sudo/Makefile | 2 +-
 security/sudo/distinfo | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)
Comment 4 Cy Schubert freebsd_committer freebsd_triage 2023-06-29 13:34:59 UTC
Thanks for approving. The commit has been pushed.