From: Peter Korsgaard <peter@korsgaard.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Olivier Schonken <olivier.schonken@gmail.com>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/4] package/libcupsfilters: new package
Date: Tue, 01 Oct 2024 22:16:28 +0200 [thread overview]
Message-ID: <87plojfujn.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240930223133.1202389-2-james.hilliard1@gmail.com> (James Hilliard's message of "Mon, 30 Sep 2024 16:31:31 -0600")
>>>>> "James" == James Hilliard <james.hilliard1@gmail.com> writes:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
We should probably use version 2.1b1 instead (or backport the fix) given
the vulnerability:
https://github.com/OpenPrinting/libcupsfilters/security/advisories/GHSA-w63j-6g73-wmg5
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-01 20:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 22:31 [Buildroot] [PATCH 1/4] package/qpdf: bump to version 11.9.1 James Hilliard
2024-09-30 22:31 ` [Buildroot] [PATCH 2/4] package/libcupsfilters: new package James Hilliard
2024-10-01 20:16 ` Peter Korsgaard [this message]
2024-10-01 20:49 ` James Hilliard
2024-10-02 6:07 ` Peter Korsgaard
2024-10-02 6:11 ` James Hilliard
2024-10-26 13:16 ` Thomas Petazzoni via buildroot
2024-09-30 22:31 ` [Buildroot] [PATCH 3/4] package/libppd: " James Hilliard
2024-10-01 20:17 ` Peter Korsgaard
2024-09-30 22:31 ` [Buildroot] [PATCH 4/4] package/cups-filters: bump to version 2.0.1 James Hilliard
2024-10-26 13:01 ` [Buildroot] [PATCH 1/4] package/qpdf: bump to version 11.9.1 Thomas Petazzoni via buildroot
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=87plojfujn.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=angelo.compagnucci@gmail.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=olivier.schonken@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.