From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136]) by lists.linuxfoundation.org (Postfix) with ESMTP id F3050C000D for ; Mon, 27 Sep 2021 01:52:45 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id DC3156067B for ; Mon, 27 Sep 2021 01:52:45 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: 0.601 X-Spam-Level: X-Spam-Status: No, score=0.601 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp3.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=tutanota.de Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iF6z6afr-UzI for ; Mon, 27 Sep 2021 01:52:44 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162]) by smtp3.osuosl.org (Postfix) with ESMTPS id BA3CE6062D for ; Mon, 27 Sep 2021 01:52:44 +0000 (UTC) Received: from w3.tutanota.de (unknown [192.168.1.164]) by w1.tutanota.de (Postfix) with ESMTP id B1B86FA0244 for ; Mon, 27 Sep 2021 01:52:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1632707561; s=s1; d=tutanota.de; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender; bh=rJ/o/q7VSToUG9PKVv2Z4EM9bAIu2UsOEtSOqlhNv1E=; b=WU7xVNanOoFUCuTldIvgU2GnWylR4h/dB9pVZ8FmmUxAZyNI8aONm+GqWOdCOIbv NMNloAm38uif9jRW1rYAep6NmoYYMGg0AjJSdPWa8v+HaaPN+4YRY4FTfAEhZq9qPGK /gubZXLKL1jGIDwK/7pG0ggnK24VsnZ62BtSulQ0/o2I7l6DLskhb5e9JBDczf4Ssza bvoM3sv5cAchyS1yx4X8VeDej/L/M9eURrPg9BoefhmvrmRgvStwJMaH3MSdnam+nT9 oWDF+3b0MBJ5pcBJUiCGVCau0obh63yCxQvkemIFBNpqFMw+rlvZYgfCECRA2UaFdd2 vH2PIQeOPg== Date: Mon, 27 Sep 2021 03:52:41 +0200 (CEST) From: Prayank To: Bitcoin Dev Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_507717_571247029.1632707561715" X-Mailman-Approved-At: Mon, 27 Sep 2021 08:02:15 +0000 Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Sep 2021 01:52:46 -0000 ------=_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
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: h= ttps://bitcoin.stackexchange.com/a/108016/

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

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:

1.Create new GitHub accounts for th= is exercise
2.Study issues in different importan= t Bitcoin projects including Bitcoin Core, LND, Libraries, Bisq, Wallets et= c.
3.Prepare pull requests to introduce some vul= nerability by fixing one of these issues
4.See h= ow 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 be= tter ways to do this.

--
Prayank

A3B1 E430 2298 178= F
------=_Part_507717_571247029.1632707561715--