From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/linux-pam: security bump to version 1.5.1
Date: Thu, 26 Nov 2020 17:06:32 +0100 [thread overview]
Message-ID: <87v9dsrtkn.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20201126192950.135871-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Thu, 26 Nov 2020 20:29:50 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fix CVE-2020-27780 - authentication bypass when a user doesn't exist and
> root password is blank
> https://github.com/linux-pam/linux-pam/releases/tag/v1.5.1
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/linux-pam/linux-pam.hash | 4 ++--
> package/linux-pam/linux-pam.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
> diff --git a/package/linux-pam/linux-pam.hash b/package/linux-pam/linux-pam.hash
> index 15e67a5e4c..10cd7be9c4 100644
> --- a/package/linux-pam/linux-pam.hash
> +++ b/package/linux-pam/linux-pam.hash
> @@ -1,6 +1,6 @@
> # Locally computed hashes after checking signature at
> -# https://github.com/linux-pam/linux-pam/releases/download/v1.5.0/Linux-PAM-1.5.0.tar.xz.asc
> +# https://github.com/linux-pam/linux-pam/releases/download/v1.5.1/Linux-PAM-1.5.1.tar.xz.asc
> # signed with the key 8C6BFD92EE0F42EDF91A6A736D1A7F052E5924BB
> -sha256 02d39854b508fae9dc713f7733bbcdadbe17b50de965aedddd65bcb6cc7852c8 Linux-PAM-1.5.0.tar.xz
> +sha256 201d40730b1135b1b3cdea09f2c28ac634d73181ccd0172ceddee3649c5792fc Linux-PAM-1.5.1.tar.xz
> # Locally computed
> sha256 133d98e7a2ab3ffd330b4debb0bfc10fea21e4b2b5a5b09de2e924293be5ff08 Copyright
> diff --git a/package/linux-pam/linux-pam.mk b/package/linux-pam/linux-pam.mk
> index 176830c1d3..61d9542c02 100644
> --- a/package/linux-pam/linux-pam.mk
> +++ b/package/linux-pam/linux-pam.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
> -LINUX_PAM_VERSION = 1.5.0
> +LINUX_PAM_VERSION = 1.5.1
Ehh, we only have 1.4.0 in master and next?
It would be good to notice that this security issue only exists in pam
1.5.0.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-11-26 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 19:29 [Buildroot] [PATCH 1/1] package/linux-pam: security bump to version 1.5.1 Fabrice Fontaine
2020-11-26 16:06 ` Peter Korsgaard [this message]
2020-11-26 16:49 ` Fabrice Fontaine
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=87v9dsrtkn.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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