From: Kleen, Andi <andi.kleen@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Security issue with vmxnet3 and e100 for AMD SEV(-SNP) / Intel TDX
Date: Mon, 11 Jan 2021 17:24:02 +0000 [thread overview]
Message-ID: <719473c603774460970f93d926530b87@intel.com> (raw)
In-Reply-To: <749d3ace-877f-1c5c-bb00-ffcb8394f36a@sect.tu-berlin.de>
>Let us know if you are interested in our fuzzing/static analysis setup.
>We're planning to submit a paper soon and we will publish the source >code along with the paper.
We already have an own static analysis/fuzzing frame work, but it's not released yet.
-Andi
next prev parent reply other threads:[~2021-01-11 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 11:57 [Intel-wired-lan] Security issue with vmxnet3 and e100 for AMD SEV(-SNP) / Intel TDX Radev, Martin
2021-01-08 15:31 ` Radev, Martin
2021-01-11 13:26 ` Kirill A. Shutemov
2021-01-11 13:56 ` Robert Buhren
2021-01-11 17:24 ` Kleen, Andi [this message]
2021-02-01 20:23 ` Ronak Doshi
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=719473c603774460970f93d926530b87@intel.com \
--to=andi.kleen@intel.com \
--cc=intel-wired-lan@osuosl.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