Bug 157646 - [RFE] Update sudo rpm from version 1.6.7 to 1.6.8
[RFE] Update sudo rpm from version 1.6.7 to 1.6.8
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: sudo (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Kopeček
BaseOS QE Security Team
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2005-05-13 09:17 EDT by Michael Small
Modified: 2012-06-20 12:13 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 12:13:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Small 2005-05-13 09:17:24 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

Description of problem:
RedHat ES and WS 4.0 currently use version 1.6.7 of sudo.  The most recent stable version of sudu, however, is 1.6.8.  The major difference between the two is support for LDAP.  This has serious administrative value (i.e. consolidated user list versus rsync of /etc/sudoers).  I would like to see RedHat ES/WS 4 enhance sudo to version 1.6.8.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. rpm -q sudo

Actual Results:  Shell displays:


Expected Results:  sudo-1.6.8...

Additional info:
Comment 3 Miroslav Suchý 2011-01-21 04:51:53 EST
Wrong component. Rassinging, but it will be most probably closed...
Comment 4 Jiri Pallich 2012-06-20 12:13:26 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.