From: Todd C. Miller <Todd.Miller@courtesan.com>
Date: Wed, 3 Nov 2010 14:03:02 +0000 (-0400)
Subject: Update 1.7.5 entries.
X-Git-Tag: SUDO_1_7_5~119
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ff30c59eb6fd21e3cece1a6cbc00ffff9ea7c4a5;p=sudo

Update 1.7.5 entries.

--HG--
branch : 1.7
---

diff --git a/NEWS b/NEWS
index 43a39643d..6f20d649d 100644
--- a/NEWS
+++ b/NEWS
@@ -14,9 +14,41 @@ What's new in Sudo 1.7.5?
    match the name used to look it up.  This may happen on some systems
    that do case insensitive lookups or that truncate long names.
 
- * Gcc will no longer display warnings on glibc systems that use
+ * GCC will no longer display warnings on glibc systems that use
    the warn_unused_result attribute for write(2) and other system calls.
 
+ * If a PAM account management module denies access, sudo now prints
+   a more useful error message and stops trying to validate the user.
+
+ * Fixed a bug introduced in sudo 1.7.3 where the ticket file was not
+   being honored when the "targetpw" sudoers Defaults option was enabled.
+
+ * Fixed a potential hang on idle systems when the sudo-run process
+   exits immediately.
+
+ * Fixed a crash when Solaris project support was enabled and the
+   -g flag was used.
+
+ * Sudo no longer exits with an error when support for
+   auditing is compiled in but auditing is not enabled.
+
+ * Fixed a crash with "sudo -l" when auditing is enabled and the
+   user is not allowed to run any commands on the host.
+
+ * Sudo will now examine all matching LDAP entries when doing a
+   lookup, even if there has already been a positive match. This
+   catches negative matches that may exist in other entries and
+   more closely match the sudoers file behavior.
+
+ * Sudo now includes a copy of zlib that will be used on systems
+   that do not have zlib installed.
+
+ * The --with-umask-override configure flag has been added to enable
+   the "umask_override" sudoers Defaults option at build time.
+
+ * Sudo now unblocks all signals on startup to avoid problems caused
+   by the parent process changing the default signal mask.
+
 What's new in Sudo 1.7.4p4?
 
  * A potential security issue has been fixed with respect to the handling