From: "Volker Weißmann" <volker.weissmann@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: University of Minnesota paper
Date: Thu, 22 Apr 2021 18:32:38 +0200 [thread overview]
Message-ID: <d85db373-c112-47e1-2efa-1f7164a255ef@gmx.de> (raw)
Hello,
I would like to inform everyone here, that I just wrote the mail below
to the authors of the paper (wu000273@umn.edu and kjlu@umn.edu).
When I receive an answer, I will post the answer here.
Mail that I sent (from my university mail address):
Hello,
I saw your paper [1
<https://raw.githubusercontent.com/QiushiWu/qiushiwu.github.io/main/papers/OpenSourceInsecurity.pdf>]
where you claimed that you proposed patches with vulnerabilities to test
the review process.
Can you prove that you just did this to test the review process and not
to actually introduce vulnerabilities.
Did you tell some trustful people in advance that you are doing this to
test the linux reviewers?
Did you gave a text that says that those patches have vulnerabilities to
a notary and told him to publish those texts after a certain date?
Did you publish a hash of a message that explains that those patches are
vulnerable in advance?
No offense, but proposing patches with vulnerabilities and then claiming
(after they got rejected) that you just did it to test the reviewers
sounds like a really lame excuse to hide something truly malicious.
[1]:
https://raw.githubusercontent.com/QiushiWu/qiushiwu.github.io/main/papers/OpenSourceInsecurity.pdf
<https://raw.githubusercontent.com/QiushiWu/qiushiwu.github.io/main/papers/OpenSourceInsecurity.pdf>
Greetings
Volker Weißmann
reply other threads:[~2021-04-22 16:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d85db373-c112-47e1-2efa-1f7164a255ef@gmx.de \
--to=volker.weissmann@gmx.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®