sudo 1.9.15b2 released

"Todd C. Miller via sudo-workers" <[email protected]> Mon, 23 Oct 2023 10:20:47 -0600
Newsgroups gmane.comp.tools.sudo.devel
Message-ID <[email protected]>
--===============8333224661878936398==
Content-Type: multipart/signed; protocol="application/pgp-signature";
  micalg=pgp-; boundary="79659_Mon_Oct_23_10_20_38_MDT_2023"

--79659_Mon_Oct_23_10_20_38_MDT_2023
Content-Type: text/plain; charset=us-ascii

The second beta release of sudo 1.9.15 is now available.  In addition
to bug fixes, sudo 1.9.15 includes changes to make it easier to
determine which sudoers rule permitted a command to be run.

Source:
    https://www.sudo.ws/dist/beta/sudo-1.9.15b2.tar.gz
    ftp://ftp.sudo.ws/pub/sudo/beta/sudo-1.9.15b2.tar.gz

SHA256 checksum:
    2d45bb219b057fe3ac872930c2c3ba974cc171b8da0ffc10e5a4028485b47119

MD5 checksum:
    49a2b4826d800b84363052ad18c8c776

Binary packages:
    https://www.sudo.ws/getting/beta_packages/

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.15b2 and 1.9.15b1:

 * New Indonesian translation from translationproject.org.

 * Updated translations from translationproject.org.

 * Sudo will now log the invoking user's environment as "submitenv"
   in the JSON logs.  The command's environment ("runenv") is no
   longer logged for commands rejected by the sudoers file or an
   approval plugin.

 * Reverted a change from sudo 1.9.4 that resulted in PAM session
   modules being called with the environment of the command to be
   run instead of the environment of the invoking user.
   GitHub issue #318.

Major changes between sudo 1.9.15b1 and 1.9.14p3:

 * Fixed an undefined symbol problem on older versions of macOS
   when "intercept" or "log_subcmds" are enabled in sudoers.
   GitHub issue #276.

 * Fixed "make check" failure related to getpwent(3) wrapping
   on NetBSD.

 * Fixed the warning message for "sudo -l command" when the command
   is not permitted.  There was a missing space between "list" and
   the actual command due to changes in sudo 1.9.14.

 * Fixed a bug where output could go to the wrong terminal if
   "use_pty" is enabled (the default) and the standard input, output
   or error is redirected to a different terminal.  Bug #1056.

 * The visudo utility will no longer create an empty file when the
   specified sudoers file does not exist and the user exits the
   editor without making any changes.  GitHub issue #294.

 * The AIX and Solaris sudo packages on www.sudo.ws now support
   "log_subcmds" and "intercept" with both 32-bit and 64-bit
   binaries.  Previously, they only worked when running binaries
   with the same word size as the sudo binary.  GitHub issue #289.

 * The sudoers source is now logged in the JSON event log.  This
   makes it possible to tell which rule resulted in a match.

 * Running "sudo -ll command" now produces verbose output that
   includes matching rule as well as the path to the sudoers file
   the matching rule came from.  For LDAP sudoers, the name of the
   matching sudoRole is printed instead.

 * The embedded copy of zlib has been updated to version 1.3.

 * The sudoers plugin has been modified to make it more resilient
   to ROWHAMMER attacks on authentication and policy matching.
   This addresses CVE-2023-42465.

 * The sudoers plugin now constructs the user time stamp file path
   name using the user-ID instead of the user name.  This avoids a
   potential problem with user names that contain a path separator
   ('/') being interpreted as part of the path name.  A similar
   issue in sudo-rs has been assigned CVE-2023-42456.

 * A path separator ('/') in a user, group or host name is now
   replaced with an underbar character ('_') when expanding escapes
   in @include and @includedir directives as well as the "iolog_file"
   and "iolog_dir" sudoers Default settings.

 * 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.  Sudo 1.9.14
   contained an incorrect fix for this.  Bug #1058.

 * Changes to terminal settings are now performed atomically, where
   possible.  If the command is being run in a pseudo-terminal and
   the user's terminal is already in raw mode, sudo will not change
   the user's terminal settings.  This prevents concurrent sudo
   processes from restoring the terminal settings to the wrong values.
   GitHub issue #312.

--79659_Mon_Oct_23_10_20_38_MDT_2023
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEWdHpzLorN2cE/dNbqfTAIc6kcPsFAmU2nVYACgkQqfTAIc6k
cPuHdA//fg0vFjV9EJu8a7Kp6uirpIjUqd4xbwqMLMby5vcUG6wAzv82/BEJGEqz
wM5mcDRWjuNK5PZy5NwJhWIbJHoEKO1PuJfYBEB+wGfwQYsiVRJMuNDofE/vBDtH
W2wTRDlxA0jBu9w/QZad7tiyY7B3T/Sp5XQdufLGW8ZzH30IUXYM0v+eNYjiGjux
EGWvaT/4GKDmPiXaKUdNtbctwEUg4xQQKAXYIhkJhSvdn7rwh2ZQKuWVUx3ffFWd
qANJ4I15KhunMTHgrNnIuLWfcA0rXZ17bwnOv9OLaFVYUDmz9DqhgEQ367zJ7RwI
fEGEwnr5QFl4gNiEg2/+tXfnUCF6ZjhL8Tc6WEo8cZpyjU+YwP82Ll23nvtqL1Lh
LEO05/hHkPb4xf/Bl0ITpb/rv63sMNE4OB/QjIcw9ZsMvhMQavbf6MolaxH9k2gX
7Sq0cd9a4H+Fm7+8VxAvUS/dGz8iP3iRLR+Xvv1eTRtI2e4hivifQ92d9VbYzIrv
xFZTaZoe76SYhyg27ggBL+43GgAOoJ3SKXQrSEhys8NxMwd3fdR0e5+s2DSVqTrq
g9dItOEVCNiMahUNEgEas6HUQyo+BszamreAK6m4qHPRjKnkYvpw2eRNJbDijmfZ
ulzjmUAlOCYSgVQWmaavw2kXOn3mIRlv/6Gv/33mZMMuet8NM+c=
=PUyV
-----END PGP SIGNATURE-----

--79659_Mon_Oct_23_10_20_38_MDT_2023--


--===============8333224661878936398==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

____________________________________________________________
sudo-workers mailing list <[email protected]>
For list information, options, or to unsubscribe, visit:
https://www.sudo.ws/mailman/listinfo/sudo-workers

--===============8333224661878936398==--