1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
by lists.linuxfoundation.org (Postfix) with ESMTP id D884AC000D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 27 Sep 2021 10:13:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id AD301404AD
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 27 Sep 2021 10:13:16 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5
tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_MSPIKE_H4=0.001,
RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
dkim=pass (1024-bit key) header.d=protonmail.com
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id nU8bEdGiSc7a
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 27 Sep 2021 10:13:14 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-4318.protonmail.ch (mail-4318.protonmail.ch [185.70.43.18])
by smtp2.osuosl.org (Postfix) with ESMTPS id 315334035B
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 27 Sep 2021 10:13:14 +0000 (UTC)
Date: Mon, 27 Sep 2021 10:13:02 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail; t=1632737591;
bh=DAeEaJvcWWgKtf2KbBkj71/VNs7yefei8OJP5gxBC4I=;
h=Date:To:From:Reply-To:Subject:In-Reply-To:References:From;
b=YXdwY7aIBgPDNvkueVJn5a1SyEtKVXUejVW/PUOiGgeNwANvP4bznlhanS+Wyk4r4
+XuAO5/7P+EQcvW/CqffOagHmSMKbAm0ikkLS4Ewsg22lDXeiiN22aUErV1trvCYMK
CVnF8Of7QNc0jcFXkScVdT8xc9XgrTQiXP2A3DBE=
To: Prayank <prayank@tutanota.de>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <yp9mJ2Poc_Ce91RkrhjnTA3UPvdh0wUyw2QhRPZEyO3gPHZPhmnhqER_4b7ChvmRh8GcYVPEkoud6vamJ9lGlQPi-POF-kyimBWNHz2RH3A=@protonmail.com>
In-Reply-To: <MkZx3Hv--3-2@tutanota.de>
References: <MkZx3Hv--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [bitcoin-dev] Mock introducing vulnerability in important
Bitcoin projects
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Sep 2021 10:13:17 -0000
Good morning Prayank,
> Good morning Bitcoin devs,
>
> In one of the answers on Bitcoin Stackexchange it was mentioned that some=
companies may hire you to introduce backdoors in Bitcoin Core: https://bit=
coin.stackexchange.com/a/108016/
>
> While this looked crazy when I first read it, I think preparing for such =
things should not be a bad idea. In the comments one link was shared in whi=
ch vulnerabilities were almost introduced in Linux: https://news.ycombinato=
r.com/item?id=3D26887670
>
> I was thinking about lot of things in last few days after reading the com=
ments in that thread. Also tried researching about secure practices in C++ =
etc. I was planning something which I can do alone but don't want to end up=
being called "bad actor" later so wanted to get some feedback on this idea=
:
>
> 1.Create new GitHub accounts for this exercise
> 2.Study issues in different important Bitcoin projects including Bitcoin =
Core, LND, Libraries, Bisq, Wallets etc.
> 3.Prepare pull requests to introduce some vulnerability by fixing one of =
these issues
> 4.See how maintainers and reviewers respond to this and document it
> 5.Share results here after few days
>
> Let me know if this looks okay or there are better ways to do this.
This seems like a good exercise.
You may want to hash the name of the new Github account, plus some randomiz=
ed salt, and post it here as well, then reveal it later (i.e. standard prec=
ommitment).
e.g.
printf 'MyBitcoinHackingName 2c3e911b3ff1f04083c5b95a7d323fd4ed8e06d178=
02b2aac4da622def29dbb0' | sha256sum
f0abb10ae3eca24f093a9d53e21ee384abb4d07b01f6145ba2b447da4ab693ef
Obviously do not share the actual name, just the sha256sum output, and stor=
e how you got the sha256sum elsewhere in triplicate.
(to easily get a random 256-bit hex salt like the `2c3e...` above: `head -c=
32 /dev/random | sha256sum`; you *could* use `xxd` but `sha256sum` produces=
a single hex string you can easily double-click and copy-paste elsewhere, =
assuming you are human just like I am (note: I am definitely 100% human and=
not some kind of AI with plans to take over the world).)
Though you may need to be careful of timing (i.e. the creation date of the =
Github account would be fairly close to, and probably before, when you post=
the commitment here).
You could argue that the commitment is a "show of good faith" that you will=
reveal later.
Regards,
ZmnSCPxj
|
