3 ms·
Try harder: https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposu...
by ck2 14y ago
Try harder:
https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposu...
- jacquesm 14y ago> Announced: 2013-05-15 How does that work? Is this a planned announcement of a known vulnerability or a typo?
- ck2 14y agoI've seen security issues given a reserved ticket number and then not disclosed until the vendor is given a certain amount of headstart? So they are maybe saying it will be disclosed in 30 days.
- jacquesm 14y agoThat's a leak in a way. It indicates that there is an unpatched vulnerability that is serious enough to warrant immediate work.
- thefrow 14y agoI don't know all the specifics, but they've pushed a patch in March for this accidental hard-fork of the blockchain with a couple months of grace period before the fix allows larger block sizes which will not be able to be processed by older clients with the bug present. See: http://mineforeman.com/2013/03/17/post-fork-plan-upgrade-your-bitcoind-client-to-0-8-1-by-15th-of-may/ http://mineforeman.com/2013/03/17/post-fork-plan-upgrade-you...
- tlrobinson 14y agoOf course no software is bug free, but this is a pretty good track record. As far as I know, none of these vulnerabilities have actually resulted in money being lost (perhaps with the exception of some mining rewards in the forks). Most of these are denial of service.