From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: "Artur Łącki" <alacki93@gmail.com>, u-boot@lists.denx.de
Cc: Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH 3/6] net: (actually/better) deal with CVE-2022-{30790, 30552}
Date: Wed, 26 Oct 2022 01:30:30 +0200 [thread overview]
Message-ID: <64cbcef3-a0a7-2394-e74c-5815dd6a7c99@prevas.dk> (raw)
In-Reply-To: <CAO=SVPQJzWfV2EmgZ8XoVfR6vL=L8R6vkE2x1GM=qr9hQvvCXg@mail.gmail.com>
On 20/10/2022 17.32, Artur Łącki wrote:
> I tested these patches with my exploit. At the moment it looks like the
> vulnerability has been fixed.
Thanks for testing. Can I/we add a "Tested-by: Artur Łącki
<alacki93@gmail.com>"?
Rasmus
next prev parent reply other threads:[~2022-10-25 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 15:32 [PATCH 3/6] net: (actually/better) deal with CVE-2022-{30790, 30552} Artur Łącki
2022-10-25 23:30 ` Rasmus Villemoes [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-18 16:41 Artur Łącki
2022-10-14 17:43 [PATCH 0/6] broken CVE fix (b85d130ea0ca) Rasmus Villemoes
2022-10-14 17:43 ` [PATCH 3/6] net: (actually/better) deal with CVE-2022-{30790,30552} Rasmus Villemoes
2022-11-28 19:51 ` Tom Rini
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=64cbcef3-a0a7-2394-e74c-5815dd6a7c99@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=alacki93@gmail.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.