Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/swupdate: bump to securoty version 2024.12.1
Date: Fri, 31 Jan 2025 22:09:10 +0100	[thread overview]
Message-ID: <e7cc9e98-e41c-4fe9-9acd-62e284ce8d81@benettiengineering.com> (raw)
In-Reply-To: <877c6a4sri.fsf@dell.be.48ers.dk>

Hi Peter,

On 1/31/25 21:45, Peter Korsgaard wrote:
>>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:
> 
>   > Fix a high severity bug with the raw handler
>   > For release note, see:
>   > https://github.com/sbabic/swupdate/releases/tag/2024.12.1
> 
> Can you confirm that this was a new issue introduced in 2024.12 and
> E.G. that 2024.11.x / 2024.02.x aren't affected?

I confirm those versions are not affected. Here you can see the only 
commit for version 2024.12.1:
https://github.com/sbabic/swupdate/commits/2024.12.1/

that is:
https://github.com/sbabic/swupdate/commit/434815b94d73c20b5461b954c4e62144ca29aa8f

and in order it Fixes:
https://github.com/sbabic/swupdate/commit/5d57a9c05ec2a4ae422bdb35247a75402f8e0aeb
and:
https://github.com/sbabic/swupdate/commit/aff67cdb2c62003a3be194036b68c62e3064d660
and both have been committed to master and 2024.12 branches
after 2024.05 tag and not in 2024.05.x tags.

So yes I confirm

Best regards
Giulio
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-01-31 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 20:18 [Buildroot] [PATCH] package/swupdate: bump to securoty version 2024.12.1 Giulio Benetti
2025-01-23 21:21 ` Julien Olivain
2025-01-31 20:45 ` Peter Korsgaard
2025-01-31 21:09   ` Giulio Benetti [this message]
2025-01-31 21:23     ` 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=e7cc9e98-e41c-4fe9-9acd-62e284ce8d81@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=buildroot@buildroot.org \
    --cc=peter@korsgaard.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