From: Angelo Compagnucci <angelo@amarulasolutions.com>
To: buildroot@buildroot.org
Cc: Angelo Compagnucci <angelo@amarulasolutions.com>
Subject: [Buildroot] [PATCH] package/cups: security bump to version 2.4.2
Date: Tue, 21 Jun 2022 23:11:40 +0200 [thread overview]
Message-ID: <20220621211140.2043539-1-angelo@amarulasolutions.com> (raw)
Fixes CVE-2022-26691
https://github.com/OpenPrinting/cups/blob/master/CHANGES.md
Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
---
package/cups/cups.hash | 2 +-
package/cups/cups.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/cups/cups.hash b/package/cups/cups.hash
index 8308b7b803..ba220e903e 100644
--- a/package/cups/cups.hash
+++ b/package/cups/cups.hash
@@ -1,4 +1,4 @@
# Locally calculated:
-sha256 c7339f75f8d4f2dec50c673341a45fc06b6885bb6d4366d6bf59a4e6c10ae178 cups-2.4.1-source.tar.gz
+sha256 f03ccb40b087d1e30940a40e0141dcbba263f39974c20eb9f2521066c9c6c908 cups-2.4.2-source.tar.gz
sha256 cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30 LICENSE
sha256 7a7bd639e3a8457ae40b0dcfb74ea3cc6a8132b06c726142e993625d33eb6de5 NOTICE
diff --git a/package/cups/cups.mk b/package/cups/cups.mk
index 298a6ed879..ab56b23bcd 100644
--- a/package/cups/cups.mk
+++ b/package/cups/cups.mk
@@ -4,7 +4,7 @@
#
################################################################################
-CUPS_VERSION = 2.4.1
+CUPS_VERSION = 2.4.2
CUPS_SOURCE = cups-$(CUPS_VERSION)-source.tar.gz
CUPS_SITE = https://github.com/OpenPrinting/cups/releases/download/v$(CUPS_VERSION)
CUPS_LICENSE = Apache-2.0 with GPL-2.0/LGPL-2.0 exception
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-06-21 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 21:11 Angelo Compagnucci [this message]
2022-06-25 6:45 ` [Buildroot] [PATCH] package/cups: security bump to version 2.4.2 Peter Korsgaard
2022-07-22 6:19 ` Peter Korsgaard
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=20220621211140.2043539-1-angelo@amarulasolutions.com \
--to=angelo@amarulasolutions.com \
--cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.