From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 47274266 for ; Sun, 10 Sep 2017 23:09:57 +0000 (UTC) X-Greylist: delayed 00:07:18 by SQLgrey-1.7.6 Received: from mail.bluematt.me (mail.bluematt.me [192.241.179.72]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E3AAF3F5 for ; Sun, 10 Sep 2017 23:09:56 +0000 (UTC) Received: from [172.17.0.2] (gw.vpn.bluematt.me [144.217.106.88]) by mail.bluematt.me (Postfix) with ESMTPSA id 4DA9413DAAD; Sun, 10 Sep 2017 23:02:37 +0000 (UTC) To: Simon Liu , Bitcoin Protocol Discussion References: <3e4541f3-f65c-5199-5e85-9a65ea5142e7@bitcartel.com> From: Matt Corallo Message-ID: Date: Sun, 10 Sep 2017 19:02:36 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <3e4541f3-f65c-5199-5e85-9a65ea5142e7@bitcartel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Responsible disclosure of bugs X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Sep 2017 23:09:57 -0000 I believe there continues to be concern over a number of altcoins which are running old, unpatched forks of Bitcoin Core, making it rather difficult to disclose issues without putting people at risk (see, eg, some of the dos issues which are preventing release of the alert key). I'd encourage the list to have a discussion about what reasonable approaches could be taken there. On 09/10/17 18:03, Simon Liu via bitcoin-dev wrote: > Hi, > > Given today's presentation by Chris Jeffrey at the Breaking Bitcoin > conference, and the subsequent discussion around responsible disclosure > and industry practice, perhaps now would be a good time to discuss > "Bitcoin and CVEs" which has gone unanswered for 6 months. > > https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-March/013751.html > > To quote: > > "Are there are any vulnerabilities in Bitcoin which have been fixed but > not yet publicly disclosed? Is the following list of Bitcoin CVEs > up-to-date? > > https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures > > There have been no new CVEs posted for almost three years, except for > CVE-2015-3641, but there appears to be no information publicly available > for that issue: > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3641 > > It would be of great benefit to end users if the community of clients > and altcoins derived from Bitcoin Core could be patched for any known > vulnerabilities. > > Does anyone keep track of security related bugs and patches, where the > defect severity is similar to those found on the CVE list above? If > yes, can that list be shared with other developers?" > > Best Regards, > Simon > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >