From: Eric Voskuil <eric@voskuil•org>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: Bitcoin Core Security Disclosure Policy
Date: Wed, 3 Jul 2024 17:44:47 -0700 (PDT) [thread overview]
Message-ID: <a9f31b7f-08c9-4ee0-97a0-1c8708ad5c63n@googlegroups.com> (raw)
In-Reply-To: <rALfxJ5b5hyubGwdVW3F4jtugxnXRvc-tjD_qwW7z73rd5j7lXGNdEHWikmSdmNG3vkSOIwEryZzOZr_DgmVDDmt9qsX0gpRAcpY9CfwSk4=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1052 bytes --]
> The project has historically done a poor job at publicly disclosing
security-critical bugs, whether externally reported or found by
contributors. This has led to a situation where a lot of users perceive
Bitcoin Core as never having bugs. This perception is dangerous and,
unfortunately, not accurate.
I have to say this is one of the most compelling statements I've seen from
the bitcoind/Bitcoin Core team in over 10 years. Many other projects have
been on the receiving end of this misperception, and it has in fact caused
material harm to the community. I don't know what precipitated this change,
but props to you all for stepping up.
Best,
Eric
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/a9f31b7f-08c9-4ee0-97a0-1c8708ad5c63n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1340 bytes --]
prev parent reply other threads:[~2024-07-04 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 12:57 [bitcoindev] " 'Antoine Poinsot' via Bitcoin Development Mailing List
2024-07-04 0:44 ` Eric Voskuil [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=a9f31b7f-08c9-4ee0-97a0-1c8708ad5c63n@googlegroups.com \
--to=eric@voskuil$(echo .)org \
--cc=bitcoindev@googlegroups.com \
/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