From: Peter Korsgaard <peter@korsgaard.com>
To: Marcus Hoffmann <buildroot@bubu1.eu>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Oli Vogt <oli.vogt.pub01@gmail.com>,
Asaf Kahlon <asafka7@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/python-django: security bump to 5.0.2
Date: Thu, 08 Feb 2024 14:51:32 +0100 [thread overview]
Message-ID: <87cyt7ysgr.fsf@48ers.dk> (raw)
In-Reply-To: <83bcb5ed-83bb-4680-9fbb-34e3d155cd21@bubu1.eu> (Marcus Hoffmann's message of "Thu, 8 Feb 2024 14:13:42 +0100")
>>>>> "Marcus" == Marcus Hoffmann <buildroot@bubu1.eu> writes:
> Hi Peter,
> On 08.02.24 14:08, Marcus Hoffmann via buildroot wrote:
>> Minor 5.0 bugfix release [1] fixing one "moderate" severity CVE.
>> Fixes: CVE-2024-24680
>> [1]
>> https://docs.djangoproject.com/en/5.0/releases/5.0.2/#django-5-0-2-release-notes
> Buildroot stable releases should probably be updated to 4.2.10:
> https://www.djangoproject.com/weblog/2024/feb/06/security-releases/
Yes, care to send a patch?
2023.02.x is using 4.1.13, but it looks like the 4.1.x series is EOL, so
I'll also update that to 4.2.10.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-08 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 13:08 [Buildroot] [PATCH] package/python-django: security bump to 5.0.2 Marcus Hoffmann via buildroot
2024-02-08 13:13 ` Marcus Hoffmann via buildroot
2024-02-08 13:51 ` Peter Korsgaard [this message]
2024-02-08 14:29 ` Peter Korsgaard
2024-03-08 14:40 ` 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=87cyt7ysgr.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=asafka7@gmail.com \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=oli.vogt.pub01@gmail.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