Date: Mon, 27 Sep 2021 03:52:41 +0200 (CEST)
From: Prayank <prayank@tutanota.de>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <MkZx3Hv--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
 boundary="----=_Part_507717_571247029.1632707561715"
Subject: [bitcoin-dev] Mock introducing vulnerability in important Bitcoin
	projects
Precedence: list

------=_Part_507717_571247029.1632707561715
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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://bitcoin.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 which vulnerabilities were almost introduced in Linux: https://news.ycombinator.com/item?id=26887670

I was thinking about lot of things in last few days after reading the comments 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.

-- 
Prayank

A3B1 E430 2298 178F

------=_Part_507717_571247029.1632707561715
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8=
">
  </head>
  <body>
<div>Good morning Bitcoin devs,<br></div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">In one of the answers on Bitcoin Stackexchange it was mentioned=
 that some companies may hire you to introduce backdoors in Bitcoin Core: h=
ttps://bitcoin.stackexchange.com/a/108016/<br></div><div><br></div><div dir=
=3D"auto"><div>While this looked crazy when I first read it, I think prepar=
ing for such things should not be a bad idea. In the comments one link was =
shared in which vulnerabilities were almost introduced in Linux: https://ne=
ws.ycombinator.com/item?id=3D26887670<br></div><div><br></div><div>I was th=
inking about lot of things in last few days after reading the comments in t=
hat 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 cal=
led "bad actor" later so wanted to get some feedback on this idea:<br></div=
><div><br></div></div><div dir=3D"auto">1.Create new GitHub accounts for th=
is exercise<br></div><div dir=3D"auto">2.Study issues in different importan=
t Bitcoin projects including Bitcoin Core, LND, Libraries, Bisq, Wallets et=
c.<br></div><div dir=3D"auto">3.Prepare pull requests to introduce some vul=
nerability by fixing one of these issues<br></div><div dir=3D"auto">4.See h=
ow maintainers and reviewers respond to this and document it<br></div><div =
dir=3D"auto">5.Share results here after few days<br></div><div dir=3D"auto"=
><br></div><div dir=3D"auto">Let me know if this looks okay or there are be=
tter ways to do this.<br></div><div dir=3D"auto"><br></div><div>-- <br></di=
v><div>Prayank<br></div><div><br></div><div dir=3D"auto">A3B1 E430 2298 178=
F<br></div>  </body>
</html>

------=_Part_507717_571247029.1632707561715--