From: Anthony Towns <aj@erisian•com.au>
To: Prayank <prayank@tutanota•de>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Mock introducing vulnerability in important Bitcoin projects
Date: Fri, 19 Aug 2022 13:09:46 +1000 [thread overview]
Message-ID: <Yv7++q6o+dtR01gT@erisian.com.au> (raw)
In-Reply-To: <MoojKWD--3-2@tutanota.de>
On Thu, Nov 18, 2021 at 09:29:24PM +0100, Prayank via bitcoin-dev wrote:
> After reading all the emails, personally experiencing review process especially on important issues like privacy and security, re-evaluating everything and considering the time I can spend on this, I have decided to do this exercise for 3 projects with just 1 account. I have created a salted hash for the username as you had mentioned in the first email:
> f40bcb13dbcbf7b6245becb757777586c22798ed7360cd9853572152ddf07a39
> 3 Bitcoin projects are Bitcoin Core (full node implementation), LND (LN implementation) and Bisq (DEX).
> Pull requests will be created in next 6 months. If vulnerability gets caught during review, will publicly announce here that the project caught the PR and reveal the de-commitment publicly. If not caught during review, will privately reveal both the inserted vulnerability and the review failure via the normal private vulnerability-reporting channels. A summary with all the details will be shared later.
It's now been nine months since this email, but I don't believe
there's been any public report on this exercise. Does this mean that a
vulnerability has been introduced in one or all of the named projects?
Cheers,
aj
prev parent reply other threads:[~2022-08-19 3:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 1:52 Prayank
2021-09-27 10:13 ` ZmnSCPxj
2021-09-27 23:19 ` Prayank
2021-09-30 20:36 ` Ruben Somsen
2021-10-01 3:03 ` Prayank
2021-10-01 12:27 ` ZmnSCPxj
2021-10-01 15:55 ` Prayank
2021-10-01 20:15 ` Ryan Grant
2021-10-02 9:19 ` Prayank
2021-10-03 9:11 ` Manuel Costa
2021-10-03 21:33 ` Luke Dashjr
2021-10-04 3:59 ` ZmnSCPxj
2021-11-18 20:29 ` Prayank
2022-08-19 3:09 ` Anthony Towns [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=Yv7++q6o+dtR01gT@erisian.com.au \
--to=aj@erisian$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=prayank@tutanota$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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