From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: U-Boot is in need of an update
Date: Mon, 13 Jun 2022 16:44:04 +0100 [thread overview]
Message-ID: <6593EDED-F628-4ED3-B742-FDE6B0865F70@ipfire.org> (raw)
In-Reply-To: <68db06b8-2470-6065-eaeb-d9542bc6e19e@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
Hello,
This email isn’t quite for me, but I wanted to chime in :)
> On 9 Jun 2022, at 21:07, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello Arne,
>
> first and foremost, I hope you are well or at least being on the path of recovery.
>
> The other day, I stumbled across https://research.nccgroup.com/2022/06/03/technical-advisory-multiple-vulnerabilities-in-u-boot-cve-2022-30790-cve-2022-30552/,
> which reminded me again of wanting to ask you about an update of U-Boot. Since I
> do not have any ARM installations in production, and certainly do not have both
> experience and a hardware arsenal close to yours, it would be great if you could
> have a look at it.
The vulnerabilities are in the IP stack which we don’t use. However, that is not a reason to not update.
> By the way: For Core Update 169, I currently plan to ship both a (smaller) linux-
> firmware update and a new kernel. According to the nightly build, we are currently
> at 21 MByte, so this might fit in. :-)
Those changes will have to be tested with all the boards. I suppose there is a rather large chance that things can break from one release to another, because not even upstream can test on all the hardware.
-Michael
>
> Have a nice weekend!
>
> Thanks, and best regards,
> Peter Müller
prev parent reply other threads:[~2022-06-13 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 20:07 Peter Müller
2022-06-13 15:44 ` Michael Tremer [this message]
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=6593EDED-F628-4ED3-B742-FDE6B0865F70@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox