rich1.0npub12p7jzesdg8kxdg8rujr20znnd868fgugczkwh4cyxwa6gnxj5sxsnjs309https://nostr.ae/npub12p7jzesdg8kxdg8rujr20znnd868fgugczkwh4cyxwa6gnxj5sxsnjs309njumphttps://nostr.ae📅 Original date posted:2017-09-10 📝 Original message:I don't think we should put any Bitcoin users at additional risk to help altcoins. If they fork the code they are making maintenance their own responsibly. It's hard to disclose a bitcoin vulnerability considering the network is decentralised and core can't force everyone to update. Maybe a timeout period for vulnerabilities could be decided. People might be expected to patched before then at which point the vulnerability can be published. Is that not already sort of how it works? On Sep 10, 2017 4:10 PM, "Matt Corallo via bitcoin-dev" < bitcoin-dev at lists.linuxfoundation.org> wrote: > 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 at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170910/1b3bfb59/attachment.html>