public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] sudo: Update to version 1.9.15p5
Date: Wed, 03 Jan 2024 21:25:00 +0000	[thread overview]
Message-ID: <a60a29b3-4a08-4e38-b69d-8fc4c402a65d@ipfire.org> (raw)
In-Reply-To: <20231231204927.3367253-1-adolf.belka@ipfire.org>

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

Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>

> - Update from version 1.9.15p4 to 1.9.15p5
> - Update of rootfile not required
> - Changelog
>     1.9.15p5
> 	    Fixed evaluation of the lecture, listpw, verifypw, and fdexec sudoers Defaults
> 	     settings when used without an explicit value. Previously, if specified
> 	     without a value they were evaluated as boolean false, even when the negation
> 	     operator (’!’) was not present.
> 	    Fixed a bug introduced in sudo 1.9.14 that prevented LDAP netgroup queries
> 	     using the NETGROUP_BASE setting from being performed.
> 	    Sudo will now transparently rename a user’s lecture file from the older
> 	     name-based path to the newer user-ID-based path. GitHub issue #342.
> 	    Fixed a bug introduced in sudo 1.9.15 that could cause a memory allocation
> 	     failure if sysconf(_SC_LOGIN_NAME_MAX) fails. Bug #1066
> 
> 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 5be3c13ab..129e41e9f 100644
> --- a/lfs/sudo
> +++ b/lfs/sudo
> @@ -24,7 +24,7 @@
>  
>  include Config
>  
> -VER        = 1.9.15p4
> +VER        = 1.9.15p5
>  
>  THISAPP    = sudo-$(VER)
>  DL_FILE    = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>  
>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>  
> -$(DL_FILE)_BLAKE2 = 011d8ee099bfc16cff141dabffd0ce2befa7fdc834108759e9fdc3c2c11c3bca02eb0c410915394b1b3e3725fbb08544f98ffa584299dbce0db2b49234c0550a
> +$(DL_FILE)_BLAKE2 = 73ee598c2a2848d5be24f97492b13eba2f326c514799220e43a1aeafc6692224a7555fb7cc0a96a2720751d3e4d98e752804db589ac3c1476f24e71f5b9bc720
>  
>  install : $(TARGET)
>  

           reply	other threads:[~2024-01-03 21:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20231231204927.3367253-1-adolf.belka@ipfire.org>]

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=a60a29b3-4a08-4e38-b69d-8fc4c402a65d@ipfire.org \
    --to=peter.mueller@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