From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Asaf Kahlon <asafka7@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/python-pip: ignore CVE-2018-20225
Date: Sun, 03 Sep 2023 21:33:09 +0200 [thread overview]
Message-ID: <87o7ijjbm2.fsf@48ers.dk> (raw)
In-Reply-To: <20230902221425.3577627-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni via buildroot's message of "Sun, 3 Sep 2023 00:14:24 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> See https://security-tracker.debian.org/tracker/CVE-2018-20225 for the
> rationale of ignoring this CVE. Things basically work as intended.
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> package/python-pip/python-pip.mk | 3 +++
> 1 file changed, 3 insertions(+)
> diff --git a/package/python-pip/python-pip.mk b/package/python-pip/python-pip.mk
> index 35ad7bede2..040767930e 100644
> --- a/package/python-pip/python-pip.mk
> +++ b/package/python-pip/python-pip.mk
> @@ -12,6 +12,9 @@ PYTHON_PIP_LICENSE = MIT
> PYTHON_PIP_LICENSE_FILES = LICENSE.txt
> PYTHON_PIP_CPE_ID_VENDOR = pypa
> PYTHON_PIP_CPE_ID_PRODUCT = pip
> +# Disputed CVE: things work as designed, and only affects the
> +# --extra-index-url option. This CVE will never be fixed.
> +PYTHON_PIP_IGNORE_CVES += CVE-2018-20225
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-03 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 22:14 [Buildroot] [PATCH] package/python-pip: ignore CVE-2018-20225 Thomas Petazzoni via buildroot
2023-09-03 19:33 ` Peter Korsgaard [this message]
2023-09-14 9:48 ` 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=87o7ijjbm2.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox