From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] sudo: Update to version 1.9.12p2
Date: Thu, 19 Jan 2023 21:25:56 +0000 [thread overview]
Message-ID: <c9791721-6606-16a7-9126-fb4b1ebd2b17@ipfire.org> (raw)
In-Reply-To: <20230119190701.2901193-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2559 bytes --]
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> - Update from version 1.9.12p1 to 1.9.12p2
> - Update of rootfile not required
> - Changelog
> 1.9.12p2
> Fixed a compilation error on Linux/aarch64. GitHub issue #197.
> Fixed a potential crash introduced in the fix GitHub issue #134. If a user’s
> sudoers entry did not have any RunAs user’s set, running sudo -U otheruser -l
> would dereference a NULL pointer.
> Fixed a bug introduced in sudo 1.9.12 that could prevent sudo from creating a
> I/O files when the iolog_file sudoers setting contains six or more Xs.
> Fixed a compilation issue on AIX with the native compiler. GitHub issue #231.
> Fixed CVE-2023-22809, a flaw in sudo’s -e option (aka sudoedit) that could
> allow a malicious user with sudoedit privileges to edit arbitrary files. For
> more information, see https://www.sudo.ws/security/advisories/sudoedit_any
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/sudo | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lfs/sudo b/lfs/sudo
> index 807169c5c..ddcddf225 100644
> --- a/lfs/sudo
> +++ b/lfs/sudo
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2023 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 1.9.12p1
> +VER = 1.9.12p2
>
> THISAPP = sudo-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 976d00fb16b0d26b2714a188e379ccba102e0fa67b8ec6278e5435728af0cc9ba23d63db64a87d4e14d59cd52d3f62401943eb7c0f9c33317179ff764a9f950c
> +$(DL_FILE)_BLAKE2 = 79eac710b757acae7aa98e6e6f495a475e5236be456e4687fb1441345ee296672ff80a5a60902cffcd257aa81a01fbc3857f3c52e51bb46f56c060fd299e0c05
>
> install : $(TARGET)
>
prev parent reply other threads:[~2023-01-19 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 19:07 Adolf Belka
2023-01-19 21:25 ` Peter Müller [this message]
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=c9791721-6606-16a7-9126-fb4b1ebd2b17@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