From: Stephan Lipp <stephan.lipp@tum.de>
To: binutils@sourceware.org
Cc: "Marcel Böhme" <marcel.boehme@mpi-sp.org>,
"Thorsten Holz" <holz@cispa.de>,
"Pretschner, Alexander" <alexander.pretschner@tum.de>,
"Hassler, Keno" <keno.hassler@cispa.de>,
"Philipp Görz" <mail@philipp-goerz.com>
Subject: Automated vulnerability detection
Date: Mon, 7 Nov 2022 13:28:06 +0100 [thread overview]
Message-ID: <99fa0211-c6d0-acd4-975b-852dff21219e@tum.de> (raw)
Dear all,
Do you use static analysis tools or fuzzers to test Binutils (2.29)?
Together with Dr. Marcel Böhme (MPI-SP), Prof. Thorsten Holz (CISPA),
Prof. Alexander Pretschner (TUM), Keno Hassler, and Philipp Görz (both
also with CISPA), we are currently analyzing the strengths and
weaknesses of automated static and dynamic testing techniques in finding
vulnerabilities.
We are happy to share any insights from our analysis which might be also
helpful to you. Thank you very much in advance!
Best regards,
Stephan
next reply other threads:[~2022-11-07 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 12:28 Stephan Lipp [this message]
2022-11-08 12:47 ` Nick Clifton
2022-11-09 11:13 ` Stephan Lipp
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=99fa0211-c6d0-acd4-975b-852dff21219e@tum.de \
--to=stephan.lipp@tum.de \
--cc=alexander.pretschner@tum.de \
--cc=binutils@sourceware.org \
--cc=holz@cispa.de \
--cc=keno.hassler@cispa.de \
--cc=mail@philipp-goerz.com \
--cc=marcel.boehme@mpi-sp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).