From: Prayank <prayank@tutanota•de>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Mock introducing vulnerability in important Bitcoin projects
Date: Mon, 27 Sep 2021 03:52:41 +0200 (CEST) [thread overview]
Message-ID: <MkZx3Hv--3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1767 bytes --]
next reply other threads:[~2021-09-27 1:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 1:52 Prayank [this message]
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
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=MkZx3Hv--3-2@tutanota.de \
--to=prayank@tutanota$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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