From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] logrotate: Update to 3.20.1
Date: Mon, 30 May 2022 18:56:18 +0000 [thread overview]
Message-ID: <b3992db2-0428-49de-a1f3-c0adac57e430@ipfire.org> (raw)
In-Reply-To: <20220526152538.3482968-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2930 bytes --]
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> For details since v3.18.0 see:
> https://github.com/logrotate/logrotate/releases/tag/3.20.1
> https://github.com/logrotate/logrotate/releases/tag/3.20.0
> https://github.com/logrotate/logrotate/releases/tag/3.19.0
>
> logrotate-3.20.1
>
> drop world-readable permission on state file even when ACLs are enabled (#446)
>
> logrotate-3.20.0
>
> fix potential DoS from unprivileged users via the state file (CVE-2022-1348)
> fix a misleading debug message with copytruncate and rotate 0 (#443)
> add support for unsigned time_t (#438)
> do not lock state file /dev/null (#433)
>
> logrotate-3.19.0
>
> continue on EINTR in compressLogFile() (#430)
> enforce stricter parsing of configuration files (#427, #431)
> avoid confusing error message in debug mode (#426)
> fix full_write() on incomplete write (#415)
> do not use alloca() any more (#412)
> do not rotate hard links unless allowhardlink is used (#407)
> change directory after dropping privileges (#397)
> add defence in depth when dropping privileges (#400)
> remove invalid configuration on error (#408)
> do not open symbolic link log files by accident (#399)
> do not write state if state file is /dev/null (#395)
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> lfs/logrotate | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lfs/logrotate b/lfs/logrotate
> index 90fdd1cfa..0e66a68e9 100644
> --- a/lfs/logrotate
> +++ b/lfs/logrotate
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2020 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2022 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 = 3.18.0
> +VER = 3.20.1
>
> THISAPP = logrotate-$(VER)
> DL_FILE = logrotate-$(VER).tar.gz
> @@ -42,7 +42,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 4e78e980f2cc8e4b208c5d64df7ba173b59dbb1913a37f28e867dae71e56d50567c8614c7b9cfc04f6dee7888518b50d302f4935a248428c567d7e42a8dcbaf9
> +$(DL_FILE)_BLAKE2 = 52f1b1991f6e17d04dee3b795bd6621be707b9386cb966f1434b00f4e6d9e8242c17a88642f98db720f8eeda6c1e38d25f050eb9e9be48a8323f84c9e408cf71
>
> install : $(TARGET)
>
prev parent reply other threads:[~2022-05-30 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 15:25 Matthias Fischer
2022-05-30 18:56 ` 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=b3992db2-0428-49de-a1f3-c0adac57e430@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