Bug 1733961
Summary: | Rebase SUDO to the latest upstream version | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Radovan Sroka <rsroka> |
Component: | sudo | Assignee: | Radovan Sroka <rsroka> |
Status: | CLOSED ERRATA | QA Contact: | Dalibor Pospíšil <dapospis> |
Severity: | high | Docs Contact: | Jan Fiala <jafiala> |
Priority: | high | ||
Version: | 8.2 | CC: | acontant, dapospis, ddelcian, lmanasko, mjahoda, thgardne, tjaros |
Target Milestone: | rc | Keywords: | AutoVerified, Rebase, Triaged |
Target Release: | 8.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | sudo-1.8.29-1.el8 | Doc Type: | Enhancement |
Doc Text: |
.`sudo` rebased to 1.8.29-3.el8
`sudo` packages have been upgraded to upstream version 1.8.29-3, which provides a number of bug fixes and enhancements over the previous version. The major changes introduced by the new version are:
* `sudo` now writes Pluggable Authentication Module (PAM) messages to the user's terminal, if available, instead of the standard output or standard error output. This prevents possible confusion of PAM output and command output sent to files and pipes.
* The `notBefore` and `notAfter` options from LDAP and SSSD now work and display correctly with the `sudo -l` command.
* The `cvtsudoers` command now rejects non-LDAP Data Interchange Format (LDIF) input when converting from LDIF to `sudoers` and JSON formats.
* With the new `log_allowed` and `log_denied` settings for `sudoers`, you can disable logging and auditing of allowed and denied commands.
* You can now use `sudo` with the `-g` option to specify a group that matches any of the target user’s groups even if no groups are present in the `runas_spec` specification. Previously, you could only do so if the group matched the target user’s primary group.
* Fixed a bug that prevented `sudo` from matching the host name to the value of `ipa_hostname` from `sssd.conf`, if specified.
* A vulnerability that allowed a `sudo` user to run a command as root when the `Runas` specification disallowed `root` access with the `ALL` keyword is now fixed (CVE-2019-14287).
* The use of unknown user and group IDs for permissive `sudoers` entries, for example using the ALL keyword, is now disabled. You can enable it with the `runas_allow_unknown_id` setting (CVE-2019-19232).
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-28 16:46:14 UTC | Type: | Enhancement |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1576880, 1651662, 1679508, 1715516, 1760697 |
Comment 1
Thomas Gardner
2019-07-29 20:15:54 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:1804 |