All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Turritopsis Dohrnii Teo En Ming <tdtemccna@gmail.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, ceo@teo-en-ming-corp.com
Subject: Re: Unpatched Critical Flaws Disclosed in U-Boot Bootloader for Embedded Devices
Date: Wed, 8 Jun 2022 21:08:02 +0800	[thread overview]
Message-ID: <CACsrZYaHRR4-_CoBWy6pKypiKAfumFVYJ4wKQ1BdS_tsuQE-Dg@mail.gmail.com> (raw)
In-Reply-To: <20220607143927.GO1958597@bill-the-cat>

Dear Tom Rini,

Noted with thanks.

Regards,

Mr. Turritopsis Dohrnii Teo En Ming
Targeted Individual in Singapore
8 Jun 2022 Wed
Blogs:
https://tdtemcerts.blogspot.com/
https://tdtemcerts.wordpress.com/

On Tue, 7 Jun 2022 at 22:39, Tom Rini <trini@konsulko.com> wrote:
>
> On Tue, Jun 07, 2022 at 08:06:07PM +0800, Turritopsis Dohrnii Teo En Ming wrote:
>
> > Subject: Unpatched Critical Flaws Disclosed in U-Boot Bootloader for
> > Embedded Devices
> >
> > Good day from Singapore,
> >
> > I am sharing this news article for more awareness.
> >
> > Article: Unpatched Critical Flaws Disclosed in U-Boot Bootloader for
> > Embedded Devices
> > Link: https://thehackernews.com/2022/06/unpatched-critical-flaws-disclosed-in-u.html
>
> For the record, this was patched before the article was published and
> fixed in v2022.07-rc4.
>
> --
> Tom

      reply	other threads:[~2022-06-08 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 12:06 Unpatched Critical Flaws Disclosed in U-Boot Bootloader for Embedded Devices Turritopsis Dohrnii Teo En Ming
2022-06-07 14:39 ` Tom Rini
2022-06-08 13:08   ` Turritopsis Dohrnii Teo En Ming [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=CACsrZYaHRR4-_CoBWy6pKypiKAfumFVYJ4wKQ1BdS_tsuQE-Dg@mail.gmail.com \
    --to=tdtemccna@gmail.com \
    --cc=ceo@teo-en-ming-corp.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.