public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] sudo: Update to version 1.9.7p2
Date: Wed, 28 Jul 2021 22:46:00 +0200	[thread overview]
Message-ID: <20210728204600.2026073-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2242 bytes --]

- Update from 1.9.7p1 to 1.9.7p2
- Update of rootfile not required.
- Changelog - more details can be found at https://www.sudo.ws/changes.html
   Major changes between version 1.9.7p2 and 1.9.7p1:
     When formatting JSON output, octal numbers are now stored as strings, not numbers.
      The JSON spec does not actually support octal numbers with a 0 prefix.
     Fixed a compilation issue on Solaris 9.
     Sudo now can handle the getgroups() function returning a different number of groups
      for subsequent invocations. GitHub PR #106.
     When loading a Python plugin, python_plugin.so now verifies that the module loaded
      matches the one we tried to load. This allows sudo to display a more useful error
      message when trying to load a plugin with a name that conflicts with a Python
      module installed in the system location.
     Sudo no longer sets the the open files resource limit to unlimited while it runs.
      This avoids a problem where sudo's closefrom() emulation would need to close a
      very large number of descriptors on systems without a way to determine which ones
      are actually open.
     Sudo now includes a configure check for va_copy or __va_copy and only defines its
      own version if the configure test fails.
     Fixed a bug in sudo's utmp file handling which prevented old entries from being
      reused. As a result, the utmp (or utmpx) file was appended to unnecessarily.
      GitHub PR #107.
     Fixed a bug introduced in sudo 1.9.7 that prevented sudo_logsrvd from accepting TLS
      connections when OpenSSL is used. Bug #988.

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 lfs/sudo | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lfs/sudo b/lfs/sudo
index 9edd08961..a74c34e7e 100644
--- a/lfs/sudo
+++ b/lfs/sudo
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 1.9.7p1
+VER        = 1.9.7p2
 
 THISAPP    = sudo-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = 0ea3649ef66df80e6ecd04d45ea0f762
+$(DL_FILE)_MD5 = d6f8217bfd16649236e100c49e0a7cc4
 
 install : $(TARGET)
 
-- 
2.32.0


                 reply	other threads:[~2021-07-28 20:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210728204600.2026073-1-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox